From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Mathieu Othacehe <othacehe@gnu.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, 5 Aug 2020 08:20:31 +0200 [thread overview]
Message-ID: <20200805082031.5f965503@primarylaptop.localdomain> (raw)
In-Reply-To: <87h7tkurlr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Mon, 03 Aug 2020 09:16:16 +0200
Mathieu Othacehe <othacehe@gnu.org> wrote:
> Hello,
Hi,
> This looks fine. I pushed those two patches with edited commit
> messages.
Thanks a lot. I'll probably have more patches that I need to send it
soon but I need to find a faster way to test them.
> For future reference, very similar patches can be send in
> the same serie :).
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}
Do I need to use --compose?
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-05 6:30 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 ` Denis 'GNUtoo' Carikli [this message]
2020-08-05 7:40 ` [bug#42658] " Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805082031.5f965503@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=42658-done@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=julien@lepiller.eu \
--cc=othacehe@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.
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.