From: Tk <tk.code@protonmail.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: When you mess up submission to guix-patches
Date: Tue, 21 May 2019 10:07:02 +0000 [thread overview]
Message-ID: <OLoFuAT6AoJCdGRVmS-NK2dCuuKfDSs02rOBJ3xKqeIk-24orA-17yIcOOEF2XxDlmt2fXGbwoG-BYtRcO8H26GhvySE56ELdgffmjPpPLw=@protonmail.com> (raw)
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 .. just wait for someone to pick up that package?
Cheers,
Tk
Sent with [ProtonMail](https://protonmail.com) Secure Email.
next reply other threads:[~2019-05-21 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 10:07 Tk [this message]
2019-05-21 11:35 ` When you mess up submission to guix-patches Tobias Geerinckx-Rice
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='OLoFuAT6AoJCdGRVmS-NK2dCuuKfDSs02rOBJ3xKqeIk-24orA-17yIcOOEF2XxDlmt2fXGbwoG-BYtRcO8H26GhvySE56ELdgffmjPpPLw=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=help-guix@gnu.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.
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).