unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: 59523@debbugs.gnu.org
Subject: [bug#59523] [PATCH] doc: contributing: Note '-v REVISION' bug in 'git send-email'.
Date: Wed, 23 Nov 2022 22:31:02 +0000	[thread overview]
Message-ID: <COK150MK63DE.2954QEYNLT44@guix-framework> (raw)
In-Reply-To: <87y1s1bh9o.fsf@nckx>

On Wed Nov 23, 2022 at 7:30 PM GMT, Tobias Geerinckx-Rice wrote:
> Has this been reported upstream?

Not afaik. The person who originally noticed this said they had
considered reporting it but it looked like a pain to report. I'll
have a look myself in a moment.

    -- (




  reply	other threads:[~2022-11-23 22:32 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 [this message]
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
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=COK150MK63DE.2954QEYNLT44@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=59523@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).