Re: Suggestions for "What's cooking"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrew Ardill <andrew.ardill@xxxxxxxxx> writes:

> 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.

> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]