[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Logging granularity

From: Jeff Hinrichs <jeffh_at_delasco.com>
Date: 2003-05-18 02:03:15 CEST

Benjamin Pflugmann said:
> But it clutters the output with all the information for the other
> files, that I am often enough not interested in. Okay, an example. Try
> something like:
> $ svn log -r5554
> http://svn.collab.net/repos/svn/trunk/subversion/libsvn_wc/diff.c
> ------------------------------------------------------------------------
> rev 5554: kfogel | 2003-04-04 23:22:22 +0200 (Fri, 04 Apr 2003) | 153
> lines
> First part of issue #1100 ("imports need to do checksumming").
> Move the result checksum from apply_textdelta to close_file:
> * subversion/libsvn_wc/diff.c
> (apply_textdelta): Lose the result_checksum argument.
> (close_file): Take text_checksum argument, ignore it.
> [23 other files are part of this changeset]
> ------------------------------------------------------------------------
It appears that there is a communication gap here. svn log returns the
"commit comment" associated with the given commit not solely a file. A
commit may contain one or more files.

In the example you site, the command returns the commit comments
associated with commits that included the file in question. However,
those commit comments include more info than just that file since they are
about the changeset in total.

If you want a 1 to 1 file to commit comment mapping, check your files in 1
at a time and you will get the desired output. However, you loose the
change set functionality by checking in 1 file at a time.

OR *untried* write a commit hook that parses a formatted commit message
and adds a revision level property of "comment" to each file. Then you
could list the comment properties for the file in question.

I would add here, that I use more general comments that describe the
nature of the change with regards to the change set. If I need specifics,
I just diff the file with the prev rev and the changed comments and code
make things apparent.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 18 02:04:41 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.