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

Re: Replacement for cvs2cl, for generating ChangeLog

From
Junio C Hamano <junkio@cox.net>
Date
Feb 27, 2007, 21:50 UTC
Message-ID
<7v649nclsq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200702272227.05244.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:
Show 17 quoted lines
> tisdag 27 februari 2007 13:57 skrev Andy Parkins:
>> On Tuesday 2007 February 27 11:41, Simon Josefsson wrote:
>> 
>> > * How do I discard all locally modified or added files?  'cvs upd -C'
>> >   does some of that, but I've been using a tool 'cvsco' which quickly
>> >   restore a CVS checkout into a pristine state.
>> 
>> Not that I know of, but git has some lovely log generation tools, so I'm sure 
>> it could be easily done with a snippet of perl - or perhaps a change to git's 
>> own log generator to support
>> 
>>  git-rev-list --pretty=gnucl
>> 
> gir-rev-list ??
>
> Extend git-shortlog with --gnucl instead. What seems missing is the grouping
> of changes by date. git-shortlog only groups by author.

If GNU changelog _were_ to have one entry per day, mixing changes from different commits together, that might be a good approach. I do not think GNU changelog guideline can be _THAT_ broken.

Listing of filenames of changed files in the log, followed by short description of the nature of the change (e.g. "Updated to do blah", "New File"), shows the CVS mentality "File matters", and that was what Simon's original example showed. It's been a while I looked at the coding guideline the last time, but I think GNU convention wants you to say "filename (function)" when applicable. Which I happen to think makes much more sense than the filename alone.

The information that would appear in "log -p --pretty" output needs to be condensed to obtain such a log entry. You _could_ still do that as a built-in if you really wanted to, but I tend to think that it is much better to implement such a specialized processing (for one thing, what a function is depends on the programming language you are reading from) as an external postprocessing filter that people can more easily tweak for their specific needs.

That's why I keep stressing that one good thing about git is it is easily scriptable.

Previous: Robin RosenbergNext: Johannes Schindelin
Message 16 of 19 in “Replacement for cvs2cl, for generating ChangeLog”
  1. Simon JosefssonFeb 27, 2007
  2. Junio C HamanoFeb 27, 2007
  3. Johannes SchindelinFeb 27, 2007
  4. Sergey VlasovFeb 27, 2007
  5. gitco - replacement for cvscoSimon Josefsson, Feb 28, 2007
  6. Yann DirsonFeb 28, 2007
  7. Simon JosefssonFeb 28, 2007
  8. Johannes SchindelinFeb 27, 2007
  9. Simon JosefssonFeb 28, 2007
  10. Junio C HamanoFeb 27, 2007
  11. Johannes SchindelinFeb 27, 2007
  12. Johannes SchindelinFeb 27, 2007
  13. Andy ParkinsFeb 27, 2007
  14. Johannes SchindelinFeb 27, 2007
  15. Robin RosenbergFeb 27, 2007
  16. Junio C HamanoFeb 27, 2007
  17. Johannes SchindelinFeb 27, 2007
  18. Johannes SchindelinFeb 27, 2007
  19. Simon JosefssonFeb 28, 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.