Johannes Altmanninger

Patch series

Of 8 patch series (re-rolls counted once), 3 landed on master and 5 did not.

• mergedsequencer: avoid dropping fixup commit that targets self via commit-ishv3, Sep 24, 2022, 3e367a5f2f
• not mergedsubtree: force merge commitFeb 1, 2022
• mergedt/perf: do not run tests in user's $SHELLv2, Dec 25, 2021, 9ccab75608
• not mergedAllow to toggle revision filterNov 28, 2021
• not mergedapply: make --intent-to-add not stomp indexv3, Nov 6, 2021
• mergedDocumentation/diff-format: state in which cases porcelain status is Tv2, Oct 4, 2021, 55e7f52b40
• not mergeddiff: suppress --name-only paths where all hunks are ignoredDec 21, 2020
• not mergedrange-diff: move " ## filename ##" headers to the first columnNov 17, 2020

A series is merged when one of its patches matches a commit on master by the same author, by subject. Versions are linked when they share a patch subject. Patches reworded before landing, or applied under someone else's name, count as not merged.

Recent emails

• Sep 24, 2022sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 22, 2022Re: [PATCH v2] sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 20, 2022Re: [PATCH] sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 20, 2022Re: [PATCH] sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 20, 2022sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 18, 2022Re: [PATCH] sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 18, 2022sequencer: avoid dropping fixup commit that targets self via commit-ish
• Sep 17, 2022Re: [BUG] fixup commit is dropped during rebase if subject = branch name
• Feb 28, 2022Re: [PATCH v2] rerere-train: two fixes to the use of "git show -s"
• Feb 27, 2022Re: Re* [PATCH] rerere-train: modernise a bit
• Feb 27, 2022Re: [PATCH] rerere-train: modernise a bit
• Feb 27, 2022Re: [PATCH v3 04/15] merge-tree: implement real merges
• Feb 27, 2022Re: [PATCH v3 04/15] merge-tree: implement real merges
• Feb 3, 2022Re: [PATCH v3 04/15] merge-tree: implement real merges
• Feb 1, 2022Re: [PATCH RESEND] subtree: force merge commit
• Feb 1, 2022subtree: force merge commit
• Jan 1, 2022Re: [PATCH 2/8] merge-tree: move logic for existing merge into new function
• Jan 1, 2022Re: [PATCH 6/8] merge-ort: allow update messages to be written to different file stream
• Jan 1, 2022Re: [PATCH 4/8] merge-tree: implement real merges
• Dec 31, 2021Re: [PATCH v2 7/8] diff: add ability to insert additional headers for paths
• Dec 29, 2021Re: [PATCH v2 7/8] diff: add ability to insert additional headers for paths
• Dec 28, 2021Re: [PATCH v2 3/8] ll-merge: make callers responsible for showing warnings
• Dec 28, 2021Re: [PATCH v8 4/7] progress.c tests: test some invalid usage
• Dec 28, 2021Re: [PATCH v8 3/7] progress.c tests: make start/stop commands on stdin
• Dec 28, 2021Re: [PATCH v8 5/7] progress.c: add temporary variable from progress struct
• Dec 28, 2021Re: [PATCH v2 8/8] show, log: include conflict/warning messages in --remerge-diff headers
• Dec 28, 2021Re: [PATCH v2 7/8] diff: add ability to insert additional headers for paths
• Dec 28, 2021Re: [PATCH v2 6/8] merge-ort: format messages slightly different for use in headers
• Dec 28, 2021Re: [PATCH v2 1/8] show, log: provide a --remerge-diff capability
• Dec 28, 2021Re: [PATCH v2 3/8] ll-merge: make callers responsible for showing warnings

Search their messages