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

[PATCH v2 0/3] Fix how for-each-ref handles broken loose references

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jun 2, 2015, 15:57 UTC
Message-ID
<1433260647-18181-1-git-send-email-mhagger@alum.mit.edu>

This is a reroll of [1]. Thanks to Peff and Junio for their comments about v1.

Changes since v1:
* Use $_z40 to initialize $ZEROS in test.
* Test that "git for-each-ref --format="%(objectname) %(refname)"
  *doesn't* notice references that point at missing objects.

This patch series is also available from my GitHub account [2] as branch for-each-ref-errors.

[1] http://thread.gmane.org/gmane.comp.version-control.git/270429 [2] https://github.com/mhagger/git

Michael Haggerty (3):
  t6301: new tests of for-each-ref error handling
  for-each-ref: report broken references correctly
  read_loose_refs(): treat NULL_SHA1 loose references as broken
 builtin/for-each-ref.c         |  5 ++++
 refs.c                         |  7 ++++++
 t/t6301-for-each-ref-errors.sh | 56 ++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 68 insertions(+)
 create mode 100755 t/t6301-for-each-ref-errors.sh
-- 
2.1.4
Next: Michael Haggerty
Message 1 of 8 in “Fix how for-each-ref handles broken loose references”
  1. 0/3 Fix how for-each-ref handles broken loose referencesMichael Haggerty, Jun 2, 2015
  2. 1/3 t6301: new tests of for-each-ref error handlingMichael Haggerty, Jun 2, 2015
  3. 2/3 for-each-ref: report broken references correctlyMichael Haggerty, Jun 2, 2015
  4. 3/3 read_loose_refs(): treat NULL_SHA1 loose references as brokenMichael Haggerty, Jun 2, 2015
  5. Stefan BellerJun 2, 2015
  6. Michael HaggertyJun 2, 2015
  7. Jeff KingJun 3, 2015
  8. Junio C HamanoJun 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.