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

Re: Suggestions for "What's cooking"

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 13, 2012, 18:06 UTC
Message-ID
<7vmx0t94rc.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAH5451kmwZehys4nL+NV8m8VGjDJtkSxru3o44_J_d3jD5ipxA@mail.gmail.com>
Andrew Ardill <andrew.ardill@gmail.com> writes:
Show 11 quoted lines
> Currently, the output for each branch looks something like:
> * <branch-name> (<creation-date>) <number-of-commits>
>   (<merge-status>)
>  [list-of-commits]
>   (<branch-usage>)
> <long-description>
> <notes-and-memoranda>
> <next-steps>
>
> and these are grouped by current integration status (new, graduated,
> stalled etc)
Yes.  Thanks for a concise summary.
Show 11 quoted lines
> A format that would make this information easier for me to parse would
> be something like:
>
> <short-branch-description>
>   <long-branch-description>
>   <notes>
>   <next-steps>
>   * <branch-name> (<creation-date>) <number-of-commits>
>     (<merge-status>)
>    [list-of-commits]
>     (<branch-usage>)

I do not see how it makes any sense to have the "This is where the section begins with, and its name is this" line in the middle of a block indented in such a way. Care to explain?

I can see some people may care more about the description than the list of commits [*1*], though.

[Footnote]

*1* It however is an indication that the title of each commit needs to be improved to convey enough information so that I do not have to write the branch description myself for them.

Previous: Andrew ArdillNext: Andrew Ardill
Message 10 of 22 in “What's cooking in git.git (Sep 2012, #03; Mon, 10)”
  1. Junio C HamanoSep 10, 2012
  2. Teach rm to remove submodules unless they contain a git directoryJens Lehmann, Sep 11, 2012
  3. Junio C HamanoSep 11, 2012
  4. Suggestions for "What's cooking"Jens Lehmann, Sep 12, 2012
  5. Jeff KingSep 12, 2012
  6. Dan JohnsonSep 12, 2012
  7. Junio C HamanoSep 12, 2012
  8. Philip OakleySep 12, 2012
  9. Andrew ArdillSep 13, 2012
  10. Junio C HamanoSep 13, 2012
  11. Andrew ArdillSep 14, 2012
  12. Junio C HamanoSep 14, 2012
  13. Andrew ArdillSep 14, 2012
  14. Junio C HamanoSep 14, 2012
  15. Philip OakleySep 14, 2012
  16. Michael HaggertySep 13, 2012
  17. Philip OakleySep 13, 2012
  18. Junio C HamanoSep 13, 2012
  19. Junio C HamanoSep 14, 2012
  20. Michael HaggertySep 14, 2012
  21. Philip OakleySep 14, 2012
  22. Jens LehmannSep 12, 2012

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.