all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Vivien Kraus" <vivien@planete-kraus.eu>,
	"Christopher Baines" <mail@cbaines.net>
Cc: 59048@debbugs.gnu.org
Subject: [bug#59048] [PATCH] guix: modify-input: Recommend prepend instead of append.
Date: Sat, 05 Nov 2022 19:51:30 +0000	[thread overview]
Message-ID: <CO4MH2A96NIL.15QFTAH8TZBWY@guix-framework> (raw)
In-Reply-To: <ab8ddd08c764b36ef37818e2bfe50d23abb43f4d.camel@planete-kraus.eu>

On Sat Nov 5, 2022 at 7:47 PM GMT, Vivien Kraus wrote:
> Now, the old way I would reply to this message would be to attach an
> updated patch, but since I have been told to send patches as emails
> instead of attachments I don’t know how to proceed.

The "Single Patches" section tells you how to send a v2 patchset; this
applies equally for multiple patches:

  If you need to send a revised patch, don’t resend it like this or send a
  “fix” patch to be applied on top of the last one; instead, use git commit -a
  or git rebase to modify the commit, and use the ISSUE_NUMBER@debbugs.gnu.org
  address and the -v flag with git send-email.

    $ git commit -a
    $ git send-email -1 -a --base=auto -v REVISION \
        --to=ISSUE_NUMBER@debbugs.gnu.org


    -- (




      reply	other threads:[~2022-11-05 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 11:59 [bug#59048] [PATCH] guix: modify-input: Recommend prepend instead of append Vivien Kraus via Guix-patches via
2022-11-05 11:59 ` [bug#59048] [PATCH v2] " Vivien Kraus via Guix-patches via
2022-11-21 14:36   ` bug#59048: " Christopher Baines
2022-11-05 12:06 ` [bug#59048] [PATCH] " ( via Guix-patches via
2022-11-05 19:17 ` Christopher Baines
2022-11-05 19:47   ` Vivien Kraus via Guix-patches via
2022-11-05 19:51     ` ( via Guix-patches via [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=CO4MH2A96NIL.15QFTAH8TZBWY@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=59048@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=paren@disroot.org \
    --cc=vivien@planete-kraus.eu \
    /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.