{"thread":{"id":"53888","subject":"git - more like a feature request for pro-lifers","startedAt":"2020-07-21T08:29:02Z","lastAt":"2020-07-26T17:41:06Z","messageCount":2,"participants":["Robert Muchacki","René Scharfe"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"401802","messageId":"B56E3052-2BD5-42D5-A854-2FAB528C3214@gmail.com","threadId":"53888","inReplyTo":null,"subject":"git - more like a feature request for pro-lifers","fromName":"Robert Muchacki","fromEmail":"robert.muchacki@gmail.com","sentAt":"2020-07-21T08:28:54Z","receivedAt":"2020-07-21T08:29:02Z","isPatch":false,"sender":{"key":"robert.muchacki@gmail.com","avatar":null},"body":"Greetings!\n\nAttached is a feature request for the pro-lifers. Doesn’t seem to much work to do in the code.\n\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\nI tried to switch branches:\n```\n  > git checkout other_branch\n```\n\nWhat did you expect to happen? (Expected behavior)\nA friendly information, not confusing, not anti-life, that will tell me why the process stopped.\n\n\nWhat happened instead? (Actual behavior)\nI got a non-pro-life informatiom, that noticed that it was ABORTING.\n\nWhat's different between what you expected and what actually happened?\nIt should have been STOPPED or ENDED. ABORTING and TERMINATING is unrespectful for the unborn code.\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.27.0\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nuname: 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\ncompiler info: clang: 11.0.3 (clang-1103.0.32.59)\nlibc info: no libc information available\n\n\n[Enabled Hooks]\n"},{"id":"402059","messageId":"50665f11-7d33-050f-d4ab-512161bec4b8@web.de","threadId":"53888","inReplyTo":"B56E3052-2BD5-42D5-A854-2FAB528C3214@gmail.com","subject":"Re: git - more like a feature request for pro-lifers","fromName":"René Scharfe","fromEmail":"l.s.r@web.de","sentAt":"2020-07-26T17:40:59Z","receivedAt":"2020-07-26T17:41:06Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Am 21.07.20 um 10:28 schrieb Robert Muchacki:\n> Greetings!\n>\n> Attached is a feature request for the pro-lifers. Doesn’t seem to much work to do in the code.\n\nCommenting on attached files is hard, so here's your bug report inlined:\n\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n>\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> I tried to switch branches:\n> ```\n>   > git checkout other_branch\n> ```\n\nWhen I do that I get:\n\n   $ git init -q a; cd a; echo 1 >a; git add a; git commit -q -m1\n\n   $ git checkout other_branch\n   error: pathspec 'other_branch' did not match any file(s) known to git\n\nIf I create that branch, then I get:\n\n   $ git branch other_branch\n   $ git checkout other_branch\n   Switched to branch 'other_branch'\n\nIf I create yet another branch, commit a modification, then modify the\nfile and try to switch to that branch, I get:\n\n   $ git branch branch; echo 2 >a; git add a; git commit -q -m2\n   $ echo 3 >a\n   $ git checkout branch\n   error: Your local changes to the following files would be overwritten by checkout:\n   \ta\n   Please commit your changes or stash them before you switch branches.\n   Aborting\n\n> What did you expect to happen? (Expected behavior)\n> A friendly information, not confusing, not anti-life, that will tell me why the process stopped.\n>\n>\n> What happened instead? (Actual behavior)\n> I got a non-pro-life informatiom, that noticed that it was ABORTING.\n\nSo you got the same kind of message that I got on my third attempt\nabove, right?  That means some files were modified and switching to\nthe other branch would have destroyed those changes.  Git detected that\nand refused, to protect your code changes.\n\n> What's different between what you expected and what actually happened?\n> It should have been STOPPED or ENDED. ABORTING and TERMINATING is unrespectful for the unborn code.\n\nOverwriting unexpectedly changed files would be irresponsible, so we\nneed to keep this feature.  Users can discard changes in more targeted\nways, if that is really what they want to do.\n\nI don't see how any of git checkout's messages is unfriendly, but you\nsomehow seem to dislike the \"Aborting\" part at the end of the third\none.  https://en.wiktionary.org/wiki/abort#Verb lists nine meanings:\n\n1. To miscarry; to bring forth (non-living) offspring prematurely.\n2. To cause a premature termination of (a fetus); to end a pregnancy\n   before term.\n3. To end prematurely; to stop in the preliminary stages; to turn back.\n4. To stop or fail at something in the preliminary stages.\n5. To become checked in normal development, so as either to remain\n   rudimentary or shrink away wholly; to cease organic growth before\n   maturation; to become sterile.\n6. To cause an organism to develop minimally; to cause rudimentary\n   development to happen; to prevent maturation.\n7. To abandon a mission at any point after the beginning of the mission\n   and prior to its completion.\n8. To terminate a mission involving a missile or rocket; to destroy a\n   missile or rocket prematurely.\n9. To terminate a process prior to completion.\n\nThe third, fourth and ninth are appropriate here: A checkout was\nstarted, but had to be called off to protect uncommitted changes.\n\n\"Abending\" would also fit and it has no other meanings.  \"Staying on\ncurrent branch.\" would be more to the point.  But actually I'm not\nsure we need that last line.  It's shown to emphasize that the\nrequested action was cancelled, but I can infer that from the rest of\nthe comprehensive error message already, or even from the the fact\nthat an error was reported at all.\n\nWould that work as well for new or less technical users?  Dunno.\n\n>\n> Anything else you want to add:\n>\n> Please review the rest of the bug report below.\n> You can delete any lines you don't wish to share.\n>\n>\n> [System Info]\n> git version:\n> git version 2.27.0\n> cpu: x86_64\n> no commit associated with this build\n> sizeof-long: 8\n> sizeof-size_t: 8\n> 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\n> compiler info: clang: 11.0.3 (clang-1103.0.32.59)\n> libc info: no libc information available\n>\n>\n> [Enabled Hooks]\n\n"}]}