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

Re: [PATCH] Add --pretty=changelog

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 2, 2007, 14:09 UTC
Message-ID
<Pine.LNX.4.63.0703021419520.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<87hct4roqa.fsf@latte.josefsson.org>
Hi,
On Fri, 2 Mar 2007, Simon Josefsson wrote:
Show 7 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > I saw that in your mail already, and I find the style cvs2cl outputs 
> > ugly.
> 
> Well, if you don't follow the GNU ChangeLog format, then please call it 
> something else.  The format is well documented.

Well, it is still ugly. I mean, really ugly. Like in "it's easier to script, therefore I don't fix it" ugly.

And yes, the format is well documented. For example, it includes the function names in brackets, which both my patch and cvs2cl do not do. These function names actually got me interested, and I would have tried to generate them automatically, too.

Show 7 quoted lines
> > No charset problem. In Git commit messages, the first line is special. 
> > It is the so called "oneline" description. If you wrap the oneline, 
> > it's your fault, not Git's.
> 
> But I want more than the oneline comment in the ChangeLog?  There is no 
> size limit on ChangeLog messages, and having as much information as 
> possible available is better.

With Git, it is encouraged that you write useful commit messages. There are commits where the patch consists of just a line change, and the message of a really long text. For a good example, look at commit v1.4.0-rc1~50: the commit message has 49 lines of text, but the patch only changes 5 lines.

If you are serious about "having as much information", include the _complete_ commit message.

> Anyway, for now I'll be settling with the (just announced) git2cl since 
> it gives me the most flexibility.

In hindsight I agree with Junio that a script is better for this purpose. At least I tricked you into writing it yourself.

> If/when git core includes your patch later on, and some of my pet 
> problems are fixed, and my distribution catches up, I'll be back.
FWIW I am now opposed to inclusion of --pretty=gnucl.

Ciao, Dscho

Previous: Simon JosefssonNext: Simon Josefsson
Message 23 of 24 in “Add --pretty=changelog”
  1. Add --pretty=changelogJohannes Schindelin, Feb 27, 2007
  2. Nicolas PitreFeb 27, 2007
  3. Johannes SchindelinFeb 27, 2007
  4. Eric WongFeb 27, 2007
  5. Junio C HamanoFeb 27, 2007
  6. 4/3 Rename --pretty=changelog to --pretty=gnucl, and fix a bugJohannes Schindelin, Feb 28, 2007
  7. Nicolas PitreFeb 28, 2007
  8. --amend Rename --pretty=changelog to --pretty=gnuclJohannes Schindelin, Feb 28, 2007
  9. Junio C HamanoMar 2, 2007
  10. print_wrapped_text: fix output for negative indentJohannes Schindelin, Mar 2, 2007
  11. --pretty=gnucl: avoid line wrapping before the commaJohannes Schindelin, Mar 2, 2007
  12. Junio C HamanoMar 3, 2007
  13. Johannes SchindelinMar 3, 2007
  14. Junio C HamanoMar 3, 2007
  15. Simon JosefssonMar 1, 2007
  16. Johannes SchindelinMar 1, 2007
  17. Shawn O. PearceMar 1, 2007
  18. Johannes SchindelinMar 1, 2007
  19. Junio C HamanoMar 2, 2007
  20. Simon JosefssonMar 2, 2007
  21. Junio C HamanoMar 2, 2007
  22. Simon JosefssonMar 2, 2007
  23. Johannes SchindelinMar 2, 2007
  24. Simon JosefssonMar 3, 2007

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.