From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: git@vger•kernel.org, Ronnie Sahlberg <sahlberg@google•com>
Subject: Re: [PATCH 0/4] Make update_refs more atomic V2
Date: Thu, 10 Apr 2014 13:08:37 -0700 [thread overview]
Message-ID: <xmqqlhvdvtfe.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq38hlxbh3.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Thu, 10 Apr 2014 11:53:28 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> CC'ing Michael who has been active in this area as an area expert.
>
> Ronnie, please make it a habit to run something like
>
> $ git shortlog --no-merges --since=18.months <affected paths>...
>
> to help you decide who your series may want to be reviewed by,
> before sending them.
>
> Thanks.
Another tip. "git format-patch -v3" would produce
Subject: [PATCH v3 0/4] blah blah blah...
prev parent reply other threads:[~2014-04-10 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 18:30 [PATCH 0/4] Make update_refs more atomic V2 Ronnie Sahlberg
2014-04-10 18:30 ` [PATCH 1/4] refs.c: split writing and commiting a ref into two separate functions Ronnie Sahlberg
2014-04-10 18:30 ` [PATCH 2/4] refs.c: split delete_ref_loose() into a separate flag-for-deletion and commit phase Ronnie Sahlberg
2014-04-10 18:30 ` [PATCH 3/4] refs.c: change update_refs to run the commit loops once all work is finished Ronnie Sahlberg
2014-04-10 18:30 ` [PATCH 4/4] refs.c: sort the refs by new_sha1 and merge the two update/delete loops into one Ronnie Sahlberg
2014-04-10 19:01 ` Junio C Hamano
2014-04-10 19:40 ` Ronnie Sahlberg
2014-04-10 18:53 ` [PATCH 0/4] Make update_refs more atomic V2 Junio C Hamano
2014-04-10 20:08 ` Junio C Hamano [this message]
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=xmqqlhvdvtfe.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=sahlberg@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox