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

Re: [PATCH 0/5] RESEND: git notes

From
git@drmicha.warpmail.net <git@drmicha.warpmail.net>
Date
May 16, 2009, 15:06 UTC
Message-ID
<4A0ED68F.6060200@drmicha.warpmail.net>
In-Reply-To
<cover.1242437696.git.johan@herland.net>
Johan Herland venit, vidit, dixit 16.05.2009 03:45:
Show 20 quoted lines
> Hi,
> 
> Dscho has asked me to take over the responsibility for the js/notes
> patch series.
> 
> The following is a re-roll and resend of the patch series currently
> in pu, plus my own 2 patches for adding support for "-m" and "-F" to
> "git notes edit".
> 
> On advice from Dscho, I have squashed the current bugfix and cleanup
> patches in js/notes into the first 4 "main" patches. As a result the
> original 15 + 2 patch series is now down to 5 (4 + 1) patches.
> 
> In sum, these 5 patches produce the exact same result as the original
> js/notes series (plus my 2 patches).
> 
> I have taken the liberty of squashing the various Signed-off-by tags
> (along with their corresponding patches) into these 5 new patches.
> I hope this is OK with everybody. If not, I apologize; please tell me,
> and I will re-send.
Well, effectively you removed me (and others) from the author list :|

I think the issue with the tree difference after this series (compared to the original one) shows that this squashing action makes reviewers' lives more complicated rather than easier. If it were the other way round squashing would be fine, of course.

Michael
Show 39 quoted lines
> 
> 
> Have fun! :)
> 
> ...Johan
> 
> 
> Johan Herland (1):
>   Teach "-m <msg>" and "-F <file>" to "git notes edit"
> 
> Johannes Schindelin (4):
>   Introduce commit notes
>   Add a script to edit/inspect notes
>   Speed up git notes lookup
>   Add an expensive test for git-notes
> 
>  .gitignore                       |    1 +
>  Documentation/config.txt         |   13 +++
>  Documentation/git-notes.txt      |   60 ++++++++++++++
>  Makefile                         |    3 +
>  cache.h                          |    4 +
>  command-list.txt                 |    1 +
>  commit.c                         |    1 +
>  config.c                         |    5 +
>  environment.c                    |    1 +
>  git-notes.sh                     |  121 ++++++++++++++++++++++++++++
>  notes.c                          |  160 ++++++++++++++++++++++++++++++++++++++
>  notes.h                          |    7 ++
>  pretty.c                         |    5 +
>  t/t3301-notes.sh                 |  149 +++++++++++++++++++++++++++++++++++
>  t/t3302-notes-index-expensive.sh |   98 +++++++++++++++++++++++
>  15 files changed, 629 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/git-notes.txt
>  create mode 100755 git-notes.sh
>  create mode 100644 notes.c
>  create mode 100644 notes.h
>  create mode 100755 t/t3301-notes.sh
>  create mode 100755 t/t3302-notes-index-expensive.sh
> 
Previous: Johan HerlandNext: Johan Herland
Message 17 of 19 in “RESEND: git notes”
  1. 0/5 RESEND: git notesJohan Herland, May 16, 2009
  2. 1/5 Introduce commit notesJohan Herland, May 16, 2009
  3. 2/5 Add a script to edit/inspect notesJohan Herland, May 16, 2009
  4. 3/5 Speed up git notes lookupJohan Herland, May 16, 2009
  5. 4/5 Add an expensive test for git-notesJohan Herland, May 16, 2009
  6. 5/5 Teach "-m <msg>" and "-F <file>" to "git notes edit"Johan Herland, May 16, 2009
  7. Junio C HamanoMay 16, 2009
  8. Johan HerlandMay 16, 2009
  9. 0/5 RESEND: git notesJohan Herland, May 16, 2009
  10. Johannes SchindelinMay 20, 2009
  11. Johan HerlandMay 20, 2009
  12. 1/5 Introduce commit notesJohan Herland, May 16, 2009
  13. 2/5 Add a script to edit/inspect notesJohan Herland, May 16, 2009
  14. 3/5 Speed up git notes lookupJohan Herland, May 16, 2009
  15. 4/5 Add an expensive test for git-notesJohan Herland, May 16, 2009
  16. 5/5 Teach "-m <msg>" and "-F <file>" to "git notes edit"Johan Herland, May 16, 2009
  17. git@drmicha.warpmail.netMay 16, 2009
  18. Johan HerlandMay 16, 2009
  19. Johannes SchindelinMay 17, 2009

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.