From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Thu, 24 Mar 2016 11:53:32 +0300 [thread overview]
Message-ID: <877fgsqmsz.fsf@gmail.com> (raw)
In-Reply-To: <87y498sui6.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 23 Mar 2016 23:24:17 +0100")
Ludovic Courtès (2016-03-24 01:24 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Ricardo Wurmus (2016-03-23 10:41 +0300) wrote:
>>
>>> Chris Marusich <cmmarusich@gmail.com> writes:
>>>
>>>> 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’m using an email client in Emacs, so the email as well as the attached
>>> patch is shown in a regular text buffer. When I see the patch I can
>>> directly apply it by running “git am” on the buffer contents, or by
>>> opening a shell and running “git am” on the file associated with the
>>> buffer.
>>
>> In Magit, one can use "w w" to apply patches, and "w m" if they
>> are saved in a "maildir" file, as can be done in Gnus by selecting
>> several articles (in Summary buffer) and pressing "o".
>>
>> See (info "(magit) Applying patches") and (info "(gnus) Saving Articles")
>
> That seems less efficient than what Andy suggests (which is what I do as
> well), no?
I just named one of the possibilities. People are free to decide what
is more efficient for them :-)
--
Alex
next prev parent reply other threads:[~2016-03-24 8:53 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 [this message]
2016-03-23 16:02 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fgsqmsz.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.