Re: [PATCH v2 09/10] pretty: implement 'summary' format
- From
René Scharfe <l.s.r@web.de>
- Date
- Nov 9, 2019, 06:38 UTC
- Message-ID
- <f66f8fbe-af46-f38e-87df-fc688110610a@web.de>
- In-Reply-To
- <e74eab6d21f655698ef8b6e1286b44ea070a7af7.1573241590.git.liu.denton@gmail.com>
Am 08.11.19 um 21:08 schrieb Denton Liu:
Show 15 quoted lines
> The standard format for referencing other commits within some projects
> (such as git.git) is the summary format. This is described in
> Documentation/SubmittingPatches as
>
> If you want to reference a previous commit in the history of a stable
> branch, use the format "abbreviated hash (subject, date)",
> with the subject enclosed in a pair of double-quotes, like this:
>
> ....
> Commit f86a374 ("pack-bitmap.c: fix a memleak", 2015-03-30)
> noticed that ...
> ....
>
> Since this format is so commonly used, standardize it as a pretty
> format.If the title contains a double quote then we get results like these:
26b455f21e ("hashmap_put takes "struct hashmap_entry *"", 2019-10-06)
01991cee86 ("config/alias.txt: change " and ' to `", 2019-06-05)I noticed the lack of quoting in the code and was worried about the output being confusing or unclean, but after staring at the examples above for a while I find that it's not that bad. It's reversible by removing the outer quotes. So perhaps we can keep it like this.
René