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

Git notes list/show <revision-range>

From
Vincent van Ravesteijn <vfr@lyx.org>
Date
Apr 18, 2011, 18:19 UTC
Message-ID
<4DAC80CF.8020704@lyx.org>
Hi all,
Considering a work-flow using topic branches just as the git development uses itself, I do miss a certain feature.
When a feature/patch is proposed, it will "cook" for a while in "pu" and "next". During this period people can comment on the patch. These comments can be stored in git notes added to the commits on which is commented.

At a certain point I want to decide whether the feature can be merged into "next" or "master", so I want to collect all notes for a certain branch to see what still has to be done before this feature can be merged. One can think about this of automatically generating a "What's cooking in X" listing the topic branches and the comments for the commits in each branch.

That's why I want to (try to) implement the feature that 'git notes list' and 'git notes show' accept a revision range and collect all notes for the commits in this range.
Do you think this will be a useful feature and that it has chances to be merged into git ?
Vincent
Next: Jeff King
Message 1 of 6 in “Git notes list/show <revision-range>”
  1. Vincent van RavesteijnApr 18, 2011
  2. Jeff KingApr 18, 2011
  3. Michael J GruberApr 19, 2011
  4. Jeff KingApr 19, 2011
  5. Michael J GruberApr 20, 2011
  6. Jeff KingApr 20, 2011

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.