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

Re: [PATCH v2 0/7] Fix some problems with reflog expiration

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 2, 2015, 22:09 UTC
Message-ID
<xmqqbnkb9hmb.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1425288597-20547-1-git-send-email-mhagger@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
> This is v2 of the patch series. Thanks to Eric Sunshine, Stefan
> Beller, Peff, and Junio for their comments about v1 [1].
Thanks for a pleasant read.  Will replace what has been queued.
Previous: Michael Haggerty
Message 13 of 13 in “Fix some problems with reflog expiration”
  1. 0/7 Fix some problems with reflog expirationMichael Haggerty, Mar 2, 2015
  2. 1/7 write_ref_sha1(): remove check for lock == NULLMichael Haggerty, Mar 2, 2015
  3. 2/7 write_ref_sha1(): Move write elision test to callersMichael Haggerty, Mar 2, 2015
  4. 3/7 lock_ref_sha1_basic(): do not set force_write for missing referencesMichael Haggerty, Mar 2, 2015
  5. 4/7 struct ref_lock: delete the force_write memberMichael Haggerty, Mar 2, 2015
  6. Junio C HamanoMar 2, 2015
  7. Michael HaggertyMar 3, 2015
  8. 5/7 reflog: improve and update documentationMichael Haggerty, Mar 2, 2015
  9. Junio C HamanoMar 2, 2015
  10. Michael HaggertyMar 3, 2015
  11. 6/7 reflog_expire(): ignore --updateref for symbolic referencesMichael Haggerty, Mar 2, 2015
  12. 7/7 reflog_expire(): never update a reference to null_sha1Michael Haggerty, Mar 2, 2015
  13. Junio C HamanoMar 2, 2015

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.