From: Sean Allred <allred.sean@gmail.com>
To: phillip.wood@dunelm.org.uk
Cc: git <git@vger.kernel.org>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: What are cherry-pick's exit codes?
Date: Thu, 01 Dec 2022 08:45:16 -0600 [thread overview]
Message-ID: <87v8mvw599.fsf@gmail.com> (raw)
In-Reply-To: <40ffe56e-cec2-7130-ca4f-2186a1b7681c@dunelm.org.uk>
Phillip Wood <phillip.wood123@gmail.com> writes:
> One can get exit code 1 without conflicts. One example is when it
> cannot cherry-pick a commit because it would overwrite an untracked
> file. Another example is when a picked commit would be empty because
> the changes are already in HEAD.
These are good cases to know/test, thank you!
--
Sean Allred
prev parent reply other threads:[~2022-12-01 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 6:39 What are cherry-pick's exit codes? Sean Allred
2022-12-01 12:19 ` Ævar Arnfjörð Bjarmason
2022-12-01 13:38 ` Sean Allred
2022-12-01 14:43 ` Phillip Wood
2022-12-01 14:45 ` Sean Allred [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8mvw599.fsf@gmail.com \
--to=allred.sean@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).