From: Robert Muchacki <email@example.com> To: firstname.lastname@example.org Subject: git - more like a feature request for pro-lifers Date: Tue, 21 Jul 2020 10:28:54 +0200 [thread overview] Message-ID: <B56E3052-2BD5-42D5-A854-2FAB528C3214@gmail.com> (raw) [-- Attachment #1.1: Type: text/plain, Size: 114 bytes --] Greetings! Attached is a feature request for the pro-lifers. Doesn’t seem to much work to do in the code. [-- Attachment #1.2: git-bugreport-2020-07-21-1019.txt --] [-- Type: text/plain, Size: 1221 bytes --] Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) I tried to switch branches: ``` > git checkout other_branch ``` What did you expect to happen? (Expected behavior) A friendly information, not confusing, not anti-life, that will tell me why the process stopped. What happened instead? (Actual behavior) I got a non-pro-life informatiom, that noticed that it was ABORTING. What's different between what you expected and what actually happened? It should have been STOPPED or ENDED. ABORTING and TERMINATING is unrespectful for the unborn code. Anything else you want to add: Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.27.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 uname: Darwin 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64 compiler info: clang: 11.0.3 (clang-122.214.171.124) libc info: no libc information available [Enabled Hooks] [-- Attachment #2: Message signed with OpenPGP --] [-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-07-21 8:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 8:28 Robert Muchacki [this message] 2020-07-26 17:40 ` René Scharfe
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=B56E3052-2BD5-42D5-A854-2FAB528C3214@gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: git - more like a feature request for pro-lifers' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).