From: Leo Famulari <leo@famulari.name>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, Nils Gillmann <niasterisk@grrlz.net>
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Wed, 23 Mar 2016 12:02:17 -0400 [thread overview]
Message-ID: <20160323160217.GB2063@jasmine> (raw)
In-Reply-To: <87mvppvm4g.fsf@gmail.com>
On Tue, Mar 22, 2016 at 09:44:47PM -0700, Chris Marusich wrote:
>
> While we're talking about patches, I'm curious: how are other people
> managing the patches? In particular, what does the workflow look like
> for people who are committing? Do you manually download the patch (or
> patches) to a temporary folder, view it/them, and if you like what you
> see, commit it with "git am" to a local repo, then push to origin?
>
> I ask because when I see a patch on the email list, there seems to be a
> bit of manual work involved in actually committing it into a local repo.
I normally read the patches in mutt.
For application, it varies a bit depending on how many patches there are
and if they are in the same thread, from different people, etc.
For single patches I can use mutt's pipe command (press | in mutt) and
pipe to 'cd ~/guix && git am`.
If there are multiple messages, I tag the messages that contain the
patches I want to apply, and then save all the tagged messages to a
temporary mailbox ~/foo. Then, I just use `git am ~/foo`.
It gets a bit messy if contributors have not used git-send-email.
I bet this workflow be improved with some macros, or by using Emacs ;)
But, applying patches is definitely not a bottleneck for me yet.
next prev parent reply other threads:[~2016-03-23 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:35 [REQ/DISCUSSION] patch managing system Nils Gillmann
2016-03-21 13:58 ` Nils Gillmann
2016-03-21 14:15 ` Ricardo Wurmus
2016-03-21 14:34 ` Nils Gillmann
2016-03-21 15:10 ` Nils Gillmann
2016-03-21 16:43 ` Ludovic Courtès
2016-03-22 11:53 ` Nils Gillmann
2016-03-22 16:26 ` Ludovic Courtès
2016-03-23 4:44 ` Chris Marusich
2016-03-23 7:41 ` Ricardo Wurmus
2016-03-23 8:15 ` Chris Marusich
2016-03-23 8:57 ` Andy Wingo
2016-03-23 8:36 ` Alex Kost
2016-03-23 8:54 ` Chris Marusich
2016-03-23 22:24 ` Ludovic Courtès
2016-03-24 8:53 ` Alex Kost
2016-03-23 16:02 ` Leo Famulari [this message]
2016-04-16 11:13 ` Ludovic Courtès
2016-04-28 8:24 ` Patch tracking Ludovic Courtès
2016-04-28 11:30 ` Ben Woodcroft
2016-04-28 12:17 ` Ludovic Courtès
2016-05-02 8:25 ` Ricardo Wurmus
2016-03-21 15:48 ` [REQ/DISCUSSION] patch managing system Mathieu Lirzin
2016-03-21 16:08 ` Mathieu Lirzin
2016-03-30 20:52 ` Cyril Roelandt
2016-03-31 6:39 ` Efraim Flashner
2016-03-31 7:53 ` Ludovic Courtès
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=20160323160217.GB2063@jasmine \
--to=leo@famulari.name \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=niasterisk@grrlz.net \
/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).