From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Tk <tk.code@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: When you mess up submission to guix-patches
Date: Tue, 21 May 2019 13:35:45 +0200 [thread overview]
Message-ID: <877eak3ur2.fsf@nckx> (raw)
In-Reply-To: <OLoFuAT6AoJCdGRVmS-NK2dCuuKfDSs02rOBJ3xKqeIk-24orA-17yIcOOEF2XxDlmt2fXGbwoG-BYtRcO8H26GhvySE56ELdgffmjPpPLw=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
Tk,
Tk wrote:
> The last moment changes I made to the RMassBank package
> submission to guix-pathes cause installation error (license
> variable is a typo). How do I fix this? Should I make another
> unrelated patch submission, or follow a patch series approach,
> or ..
Please send (a) revised patch(es) to the same bug number:
$ git send-email --subject-prefix="PATCH v2" \
--in-reply-to=35810@debbugs.gnu.org […]
I guess this is what you meant above by ‘patch series’?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-05-21 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 10:07 When you mess up submission to guix-patches Tk
2019-05-21 11:35 ` Tobias Geerinckx-Rice [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
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=877eak3ur2.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=tk.code@protonmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).