From: zimoun <zimon.toutoune@gmail.com>
To: 59523@debbugs.gnu.org
Cc: "\(" <paren@disroot.org>
Subject: [bug#59523] [PATCH] doc: contributing: Note '-v REVISION' bug in 'git send-email'.
Date: Wed, 23 Nov 2022 21:47:50 +0100 [thread overview]
Message-ID: <86k03lfle1.fsf@gmail.com> (raw)
In-Reply-To: <20221123190710.26517-1-paren@disroot.org>
Hi,
On Wed, 23 Nov 2022 at 19:07, "\( via Guix-patches" via <guix-patches@gnu.org> wrote:
> Turns out that due to a bug in ``git send-email'', using ``-v 2'' with
> a space between the flag and the argument won't work. If you try it, it'll
> print a confusing error message, so this patch updates the manual to note
> this and remove the space in an example that uses it.
Arf clunky Git CLI. :-) The git-format-patch manual says:
-v <n>, --reroll-count=<n>
so the space is allowed and it seems to work. The git-send-email
manual says,
git send-email [<options>] <format-patch options>
and indeed,
--8<---------------cut here---------------start------------->8---
$ git send-email -1 -v 2 --to=trash@trash.com
fatal: ambiguous argument '2': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
format-patch -o /tmp/bin67IOTaX -1 2: command returned error: 128
--8<---------------cut here---------------end--------------->8---
But it works without the space. Arf, Git CLI…
Cheers,
simon
next prev parent reply other threads:[~2022-11-23 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 19:07 [bug#59523] [PATCH] doc: contributing: Note '-v REVISION' bug in 'git send-email' ( via Guix-patches via
2022-11-23 19:30 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-23 22:31 ` ( via Guix-patches via
2022-11-24 2:04 ` Kyle Meyer
2023-03-13 23:43 ` Kyle Meyer
2023-03-21 12:34 ` Maxim Cournoyer
2022-11-23 20:47 ` zimoun [this message]
2022-11-26 11:54 ` [bug#59523] [PATCH v2 1/3] " ( via Guix-patches via
2022-11-26 11:54 ` [bug#59523] [PATCH v2 2/3] doc: contributing: Fix incorrect guix-patches address ( via Guix-patches via
2022-11-26 11:54 ` [bug#59523] [PATCH v2 3/3] doc: contributing: Recommend --base=origin/master ( via Guix-patches via
2023-01-11 10:58 ` Christopher Baines
2023-01-11 17:05 ` ( via Guix-patches via
2022-12-02 16:09 ` [bug#59523] [PATCH v2 1/3] doc: contributing: Note '-v REVISION' bug in 'git send-email' zimoun
2023-01-11 10:57 ` Christopher Baines
2023-03-21 12:41 ` bug#59523: [PATCH] " Maxim Cournoyer
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=86k03lfle1.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=59523@debbugs.gnu.org \
--cc=paren@disroot.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.