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

[PATCHv3 0/5] Handling empty notes

From
Johan Herland <johan@herland.net>
Date
Nov 7, 2014, 09:19 UTC
Message-ID
<1415351961-31567-1-git-send-email-johan@herland.net>
Changes v1 -> v2:
 - Incorporate Eric's feedback
 - Factor out an initial fix, needed before adding the tests
Changes v2 -> v3:
 - Incorporate Junio's feedback
 - Move tests from t3312 to t3301
 - Refactor the display of empty notes (the part concerning
   git-log) into a separate follow-up patch (#4)
 - Add a final (optional) patch with some whitespace and other
   cleanups in t3301. Feel free to drop this if it's too much
   churn.
Have fun! :)
...Johan
Johan Herland (5):
  builtin/notes: Fix premature failure when trying to add the empty blob
  t3301: Verify that 'git notes' removes empty notes by default
  builtin/notes: Add --allow-empty, to allow storing empty notes
  notes: Empty notes should be shown by 'git log'
  t3301: Use write_script(), nitpick whitespace
 Documentation/git-notes.txt |  12 +-
 builtin/notes.c             |  25 ++--
 notes.c                     |   3 +-
 t/t3301-notes.sh            | 301 +++++++++++++++++++++++++-------------------
 4 files changed, 197 insertions(+), 144 deletions(-)
-- 
2.0.0.rc4.501.gdaf83ca
Next: Johan Herland
Message 1 of 12 in “[PATCHv3 0/5] Handling empty notes”
  1. Johan HerlandNov 7, 2014
  2. 1/5 builtin/notes: Fix premature failure when trying to add the empty blobJohan Herland, Nov 7, 2014
  3. 2/5 t3301: Verify that 'git notes' removes empty notes by defaultJohan Herland, Nov 7, 2014
  4. Junio C HamanoNov 7, 2014
  5. 3/5 builtin/notes: Add --allow-empty, to allow storing empty notesJohan Herland, Nov 7, 2014
  6. Junio C HamanoNov 7, 2014
  7. Johan HerlandNov 9, 2014
  8. Junio C HamanoNov 10, 2014
  9. 4/5 notes: Empty notes should be shown by 'git log'Johan Herland, Nov 7, 2014
  10. Junio C HamanoNov 7, 2014
  11. 5/5 t3301: Use write_script(), nitpick whitespaceJohan Herland, Nov 7, 2014
  12. Junio C HamanoNov 7, 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.