From: Brandon Williams <bmwill@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Eric Wong" <e@80x24.org>, "Samuel Lijin" <sxlijin@gmail.com>,
"Jonathan Tirado" <tiradojonathan32@gmail.com>,
"Jeff King" <peff@peff.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
meta@public-inbox.org
Subject: Re: vger not relaying some of Junio's messages today?
Date: Mon, 8 May 2017 10:01:36 -0700 [thread overview]
Message-ID: <20170508170136.GB179149@google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705081239360.146734@virtualbox>
On 05/08, Johannes Schindelin wrote:
> Hi Ævar,
>
> On Sat, 6 May 2017, Ævar Arnfjörð Bjarmason wrote:
>
> > I have one [script] to git am a patch from a msgid, thought I should
> > write something to handle a series in some DWIM fashion (e.g. apply the
> > latest continuous sequence of patches matching --author) but figured
> > that someone's probably wrote this already & I don't need to hack it up
> > myself...
>
> You probably missed my previous mails mentioning
>
> https://github.com/git-for-windows/build-extra/blob/master/apply-from-public-inbox.sh
>
> You can use this script to apply single patches (identified by their
> Message-ID), and patch series (identified by their cover letter's
> Message-ID).
>
> As I mentioned at the Contributors' Summit at GitMerge 2017: I would
> *love* to collaborate on tools that make any part of the
> contribution/review process less cumbersome than it is right now.
Yeah its not the most streamlined process. I'm sure everyone writes
their own scripts (like I did) tailored to their workflow. For example
I just tag a bunch of mails in mutt and then have a scripts which 'git
am's them on a branch/base of my choosing. But its specific to
my workflow so idk how useful it would be to others :(
--
Brandon Williams
next prev parent reply other threads:[~2017-05-08 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 17:46 vger not relaying some of Junio's messages today? Jonathan Tirado
2017-05-06 18:23 ` Samuel Lijin
2017-05-06 20:50 ` Eric Wong
2017-05-06 21:05 ` Ævar Arnfjörð Bjarmason
2017-05-06 21:42 ` Eric Wong
2017-05-08 10:42 ` Johannes Schindelin
2017-05-08 17:01 ` Brandon Williams [this message]
2017-05-09 10:10 ` Johannes Schindelin
2017-05-06 21:10 ` Samuel Lijin
2017-05-07 0:26 ` Eric Wong
2017-05-08 17:05 ` Brandon Williams
2017-05-07 1:05 ` Eric Wong
2017-05-07 3:00 ` Junio C Hamano
2017-05-07 3:24 ` Eric Wong
2017-05-07 12:41 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 3:57 Eric Wong
2017-01-27 4:01 ` Jeff King
2017-01-31 20:27 ` Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170508170136.GB179149@google.com \
--to=bmwill@google.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=meta@public-inbox.org \
--cc=peff@peff.net \
--cc=sxlijin@gmail.com \
--cc=tiradojonathan32@gmail.com \
/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://80x24.org/mirrors/git.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).