{"thread":{"id":"60274","subject":"Feature Request - Unique commits list","startedAt":"2023-09-28T08:17:05Z","lastAt":"2023-09-28T14:08:07Z","messageCount":3,"participants":["Saurabh Sonar","Kristoffer Haugsbakk","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"482428","messageId":"CAJ-L=uAjXB67Zx1BPpdJYF_y1RS+UqwpyTMF1F4o3yO+1o76vg@mail.gmail.com","threadId":"60274","inReplyTo":null,"subject":"Feature Request - Unique commits list","fromName":"Saurabh Sonar","fromEmail":"saurabh.sonar120@gmail.com","sentAt":"2023-09-28T08:16:37Z","receivedAt":"2023-09-28T08:17:05Z","isPatch":false,"sender":{"key":"saurabh.sonar120@gmail.com","avatar":null},"body":"After merging the master branch into my local it is hard to find my\nown commits in git history.\n\nTo solve this issue I suggest, There should be an option to find out\nwhich commits are only present in only current branch and not present\nin any other.\n\nThe user should be aware that if he deletes the branch some list of\ncommits are not merged or present in any other branch and he is going\nto lose them forever.\n"},{"id":"482429","messageId":"8e315d35-7076-47e8-b3a5-6330587325e8@app.fastmail.com","threadId":"60274","inReplyTo":"CAJ-L=uAjXB67Zx1BPpdJYF_y1RS+UqwpyTMF1F4o3yO+1o76vg@mail.gmail.com","subject":"Re: Feature Request - Unique commits list","fromName":"Kristoffer Haugsbakk","fromEmail":"code@khaugsbakk.name","sentAt":"2023-09-28T08:21:21Z","receivedAt":"2023-09-28T08:21:48Z","isPatch":false,"sender":{"key":"code@khaugsbakk.name","avatar":"https://avatars.githubusercontent.com/u/2229597?v=4"},"body":"On Thu, Sep 28, 2023, at 10:16, Saurabh Sonar wrote:\n> The user should be aware that if he deletes the branch some list of\n> commits are not merged or present in any other branch and he is going\n> to lose them forever.\n\nThat already happens now, though? (Well, not “forever” because of GC and\nwhatnot.) You have to force the deletion with `-D` if the branch is not in\nthe “upstream” branch.\n\n-- \nKristoffer Haugsbakk\n"},{"id":"482432","messageId":"xmqqbkdml7b8.fsf@gitster.g","threadId":"60274","inReplyTo":"CAJ-L=uAjXB67Zx1BPpdJYF_y1RS+UqwpyTMF1F4o3yO+1o76vg@mail.gmail.com","subject":"Re: Feature Request - Unique commits list","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-09-28T14:07:55Z","receivedAt":"2023-09-28T14:08:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Saurabh Sonar <saurabh.sonar120@gmail.com> writes:\n\n> After merging the master branch into my local it is hard to find my\n> own commits in git history.\n\nI suspect the above may be the other way around (i.e., after the\nupstream takes some but not all of my changes into their 'master'\nbranch, I want to find out what remaining topics from me are still\nnot accepted by them), but anyway, doesn't something along the lines\nof\n\n\t$ git log --branches --not origin/master\n\nwork for you?  It asks\n\n * Please list commits (\"git log\")\n\n * The commits to be listed should be discovered by traversing the\n   history starting from my branch tips (\"--branches\")\n\n * But I am not interested in those commits that can be reached from\n   the 'master' branch of my upstream (\"--not origin/master\").\n\n"}]}