git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/4] Make update_refs more atomic V2

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 10, 2014, 20:08 UTC
Message-ID
<xmqqlhvdvtfe.fsf@gitster.dls.corp.google.com>
In-Reply-To
<xmqq38hlxbh3.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 10 quoted lines
> 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...
Previous: Junio C Hamano
Message 9 of 9 in “Make update_refs more atomic V2”
  1. 0/4 Make update_refs more atomic V2Ronnie Sahlberg, Apr 10, 2014
  2. 1/4 refs.c: split writing and commiting a ref into two separate functionsRonnie Sahlberg, Apr 10, 2014
  3. 2/4 refs.c: split delete_ref_loose() into a separate flag-for-deletion and commit phaseRonnie Sahlberg, Apr 10, 2014
  4. 3/4 refs.c: change update_refs to run the commit loops once all work is finishedRonnie Sahlberg, Apr 10, 2014
  5. 4/4 refs.c: sort the refs by new_sha1 and merge the two update/delete loops into oneRonnie Sahlberg, Apr 10, 2014
  6. Junio C HamanoApr 10, 2014
  7. Ronnie SahlbergApr 10, 2014
  8. Junio C HamanoApr 10, 2014
  9. Junio C HamanoApr 10, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.