git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Andy Parkins <andyparkins@gmail.com>,
	git@vger.kernel.org, Simon Josefsson <simon@josefsson.org>
Subject: Re: Replacement for cvs2cl, for generating ChangeLog
Date: Tue, 27 Feb 2007 13:50:29 -0800	[thread overview]
Message-ID: <7v649nclsq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200702272227.05244.robin.rosenberg.lists@dewire.com> (Robin Rosenberg's message of "Tue, 27 Feb 2007 22:27:05 +0100")

Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:

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

  reply	other threads:[~2007-02-27 21:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 11:41 Replacement for cvs2cl, for generating ChangeLog Simon Josefsson
2007-02-27 12:23 ` Junio C Hamano
2007-02-27 12:37 ` Johannes Schindelin
2007-02-27 14:40   ` Sergey Vlasov
2007-02-28 14:08     ` gitco - replacement for cvsco Simon Josefsson
2007-02-28 19:55       ` Yann Dirson
2007-02-28 21:31         ` Simon Josefsson
2007-02-27 15:19   ` Replacement for cvs2cl, for generating ChangeLog Johannes Schindelin
2007-02-28 14:12     ` Simon Josefsson
2007-02-27 19:27   ` Junio C Hamano
2007-02-27 19:45     ` Johannes Schindelin
2007-02-27 20:54       ` Johannes Schindelin
2007-02-27 12:57 ` Andy Parkins
2007-02-27 15:56   ` Johannes Schindelin
2007-02-27 21:27   ` Robin Rosenberg
2007-02-27 21:50     ` Junio C Hamano [this message]
2007-02-27 22:22       ` Johannes Schindelin
2007-02-27 22:12     ` Johannes Schindelin
2007-02-28 14:27       ` Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7v649nclsq.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    --cc=simon@josefsson.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).