unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: Danny Milosavljevic <dannym@scratchpost.org>,
	Julien Lepiller <julien@lepiller.eu>,
	42658-done@debbugs.gnu.org
Subject: [bug#42658] [PATCH 1/2] gnu: android: export android-libcutils
Date: Wed, 05 Aug 2020 09:40:25 +0200	[thread overview]
Message-ID: <87r1sl35hy.fsf@gnu.org> (raw)
In-Reply-To: <20200805082031.5f965503@primarylaptop.localdomain> (Denis Carikli's message of "Wed, 5 Aug 2020 08:20:31 +0200")


Hello,

> How do I do that? I used the following command to send the patch:
>> git send-email --to="guix-patches@gnu.org" \
>> 	--cc="Julien Lepiller <julien@lepiller.eu>" \
>> 	--cc="Danny Milosavljevic <dannym@scratchpost.org>" \
>> 	0001-gnu-android-export-android-libcutils.patch \
>> 	0002-gnu-android-export-android-liblog.patch \
>> 	${sentinel}

Each time a mail is sent to "guix-patches@gnu.org" a new bug ticket is
created. You should first send either the cover letter or the first
patch, and then send all the subsequent patches to NNN@debbugs.gnu.org
where NNN is the ticket number created when the first patch is sent.

See the bottom of
https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html for
further explications.

Thanks,

Mathieu




  reply	other threads:[~2020-08-05  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01 20:16 [bug#42658] [PATCH 1/2] gnu: android: export android-libcutils Denis 'GNUtoo' Carikli
2020-08-01 20:16 ` [bug#42659] [PATCH 2/2] gnu: android: export android-liblog Denis 'GNUtoo' Carikli
2020-08-03  7:16 ` bug#42658: [PATCH 1/2] gnu: android: export android-libcutils Mathieu Othacehe
2020-08-05  6:20   ` [bug#42658] " Denis 'GNUtoo' Carikli
2020-08-05  7:40     ` Mathieu Othacehe [this message]
2020-08-05  9:11       ` Denis 'GNUtoo' Carikli

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=87r1sl35hy.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=42658-done@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=dannym@scratchpost.org \
    --cc=julien@lepiller.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 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).