# [Proposal] git am --check 4 messages from 2019-06-02 to 2019-06-03. Participants: Drew DeVault, Christian Couder, Duy Nguyen, Junio C Hamano. Thread: https://gitlist.dev/t/51225 ## Drew DeVault, 2019-06-02 17:37 Subject: [Proposal] git am --check Message-ID: URL: https://gitlist.dev/e/BUJFK0ZEKP5I.16DDFWUTXGJTE%40homura ``` This flag would behave similarly to git apply --check, or in other words would exit with a nonzero status if the patch is not applicable without actually applying the patch otherwise. Rationale: I'm working on an email client which has some git integration, and when you scroll over a patch I want to quickly test its applicability and show an indication of the result. Thoughts on the approach are welcome; my initial naive patch just tried to add --check to the apply flags but that didn't work as I had hoped. Will take another crack at a patch soon(ish). ``` ## Christian Couder, 2019-06-03 09:28 Subject: Re: [Proposal] git am --check Message-ID: URL: https://gitlist.dev/e/CAP8UFD1W_tB34N-uAA85%2BQkHY6kmGWYYM47zceP3%3D5aTwxwvnQ%40mail.gmail.com In-Reply-To: ``` On Sun, Jun 2, 2019 at 7:38 PM Drew DeVault wrote: > > This flag would behave similarly to git apply --check, or in other words > would exit with a nonzero status if the patch is not applicable without > actually applying the patch otherwise. `git am` uses the same code as `git apply` to apply patches, so there should be no difference between `git am --check` and `git apply --check`. > Rationale: I'm working on an email client which has some git > integration, and when you scroll over a patch I want to quickly test its > applicability and show an indication of the result. > > Thoughts on the approach are welcome; my initial naive patch just tried > to add --check to the apply flags but that didn't work as I had hoped. > Will take another crack at a patch soon(ish). Could you tell us about what didn't work as you hoped? And how `git am --check` would be different from `git apply --check`? ``` ## Duy Nguyen, 2019-06-03 09:35 Subject: Re: [Proposal] git am --check Message-ID: URL: https://gitlist.dev/e/CACsJy8CUGfUwi15%2BggOgRT4xotCkJVhGtCrjMa%3D4pdnDq25f4A%40mail.gmail.com In-Reply-To: ``` On Mon, Jun 3, 2019 at 4:29 PM Christian Couder wrote: > > On Sun, Jun 2, 2019 at 7:38 PM Drew DeVault wrote: > > > > This flag would behave similarly to git apply --check, or in other words > > would exit with a nonzero status if the patch is not applicable without > > actually applying the patch otherwise. > > `git am` uses the same code as `git apply` to apply patches, so there > should be no difference between `git am --check` and `git apply > --check`. One difference (that still annoys me) is "git apply" must be run at topdir. "git am" can be run anywhere and it will automatically find topdir. "git am" can also consume multiple patches, so it's some extra work if we just use "git apply" directly, although I don't think that's a very good argument for "am --check". -- Duy ``` ## Junio C Hamano, 2019-06-03 18:16 Subject: Re: [Proposal] git am --check Message-ID: URL: https://gitlist.dev/e/xmqqblzev8jw.fsf%40gitster-ct.c.googlers.com In-Reply-To: ``` Duy Nguyen writes: > On Mon, Jun 3, 2019 at 4:29 PM Christian Couder > wrote: >> >> On Sun, Jun 2, 2019 at 7:38 PM Drew DeVault wrote: >> > >> > This flag would behave similarly to git apply --check, or in other words >> > would exit with a nonzero status if the patch is not applicable without >> > actually applying the patch otherwise. >> >> `git am` uses the same code as `git apply` to apply patches, so there >> should be no difference between `git am --check` and `git apply >> --check`. > > One difference (that still annoys me) is "git apply" must be run at > topdir. "git am" can be run anywhere and it will automatically find > topdir. > > "git am" can also consume multiple patches, so it's some extra work if > we just use "git apply" directly, although I don't think that's a very > good argument for "am --check". Another is that "am" has preprocessing phase performed by mailsplit that deals with MIME garbage, which "apply" will totally choke on without even attempting to cope with. I haven't carefully read the "proposal" or any rfc patches yet, but would/should the command make a commit if the patch cleanly applies? I wonder if a "--dry-run" option is more useful (i.e. checks and reports with the exit status *if* the command without "--dry-run" would cleanly succeed, but never makes a commit or touches the index or the working tree), given the motivating use case is a Git aware MUA that helps the user by saying "if you are busy you could perhaps skip this message as the patch would not apply to your tree anyway". ```