From: Vinicius Monego <monego@posteo.net>
To: Brett Gilio <brettg@gnu.org>
Cc: 42741@debbugs.gnu.org
Subject: [bug#42741] [PATCH 1/4] gnu: Add python-outcome.
Date: Fri, 07 Aug 2020 16:30:47 -0300 [thread overview]
Message-ID: <87imduuuc8.fsf@posteo.net> (raw)
In-Reply-To: <87zh7647nf.fsf@gnu.org>
Brett Gilio writes:
> Hi Vinicius!
>
> Thanks for your patch series. I just wanted to let you know that best
> practice is to send patch series all to the same bug number instead of
> opening a new bug number for each patch in the series. Thanks! :)
Hello Brett.
Sure, but that's a problem I'm having with git. I use `git format-patch
[branch] -o folder/` and `git send-email --to="[this list]"
folder/`. Sometimes it sends to one number, sometimes it sends to
different numbers.
I sent two different series for python-h2 and python-sniffio two days
ago using the very same procedure for both. The latter was sent correctly while
the former was sent to different numbers.
Am I missing something?
next prev parent reply other threads:[~2020-08-07 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 13:24 [bug#42741] [PATCH 1/4] gnu: Add python-outcome Vinicius Monego
2020-08-07 13:24 ` [bug#42742] [PATCH 2/4] gnu: Add python-trustme Vinicius Monego
2020-08-09 11:55 ` bug#42742: " Efraim Flashner
2020-08-07 13:24 ` [bug#42743] [PATCH 3/4] gnu: Add python-trio Vinicius Monego
2020-08-09 11:56 ` bug#42743: " Efraim Flashner
2020-08-07 13:24 ` [bug#42744] [PATCH 4/4] gnu: Add python-pytest-trio Vinicius Monego
2020-08-09 11:56 ` bug#42744: " Efraim Flashner
2020-08-07 18:45 ` [bug#42741] [PATCH 1/4] gnu: Add python-outcome Brett Gilio
2020-08-07 19:30 ` Vinicius Monego [this message]
2020-08-08 13:35 ` Vinicius Monego
2020-08-09 11:55 ` bug#42741: " Efraim Flashner
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=87imduuuc8.fsf@posteo.net \
--to=monego@posteo.net \
--cc=42741@debbugs.gnu.org \
--cc=brettg@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 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).