From: Leo Famulari <leo@famulari.name>
To: Dylan Jeffers <sapientech@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-pypump
Date: Sat, 13 Aug 2016 08:57:00 -0400 [thread overview]
Message-ID: <20160813125700.GA12089@jasmine> (raw)
In-Reply-To: <20160812183129.0f76b28a@openmailbox.org>
On Fri, Aug 12, 2016 at 06:31:29PM -0700, Dylan Jeffers wrote:
> When submitting patches that require other patches I've submitted,
> should I put them together in a single patch, or keep them separate
> like this?
For patches that depend on each other, sending them as a "patch series"
will communicate the dependencies and ensure that they apply properly.
If you've made your patches on a branch besides master, you can do:
$ git format-patch -n master
... and attach those patches to an email.
You can also use `git send-email`, which uses `git format-patch` but
will also send the patch series if you set up SMTP and configure Git to
use it.
Can you resubmit these two patches using that method? Normally I
wouldn't ask you to do that but, in this case, this patch does not apply
cleanly after having applied the patch for python-requests-oauthlib;
they both have the same leading context:
> @@ -9852,3 +9853,34 @@ etc.")
> (package
> (inherit base)
> (name "ptpython2"))))
Thanks!
next prev parent reply other threads:[~2016-08-13 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 1:31 [PATCH] gnu: Add python-pypump Dylan Jeffers
2016-08-13 12:57 ` Leo Famulari [this message]
2016-08-13 19:32 ` Dylan Jeffers
2016-08-13 23:07 ` Leo Famulari
2016-08-14 23:07 ` Dylan Jeffers
2016-08-15 18:41 ` Leo Famulari
2016-08-15 22:17 ` Dylan Jeffers
2016-08-19 22:17 ` Leo Famulari
2016-09-05 9:21 ` Efraim Flashner
2016-08-15 22:29 ` Danny Milosavljevic
2016-08-15 22:41 ` Leo Famulari
2016-08-16 18:02 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2017-01-09 10:03 [PATCH 0/9] Add more qtmodules Efraim Flashner
2017-01-09 10:03 ` [PATCH] gnu: Add python-pypump Efraim Flashner
2017-01-09 11:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160813125700.GA12089@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=sapientech@openmailbox.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.