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

Re: [Issue 802] Changed - No separation between files when svn log on multiple files

From: Eric Gillespie <epg_at_pretzelnet.org>
Date: 2002-07-21 06:15:09 CEST

> + ------- Additional Comments From kfogel@tigris.org 2002-07-20 20:23 PDT --

> + This is because Subversion log entries are attached to revisions, not
> + files.

Er, huh? Log entries are attached to revisions in CVS too.

> + When you run "svn log FILE_A FILE_B", you're really saying "show me
> + logs for all the revisions in which either FILE_A or FILE_B, or both,
> + changed". Note that any given revision log should only be printed out

No, that's what you thought users would say. That's not what i
said when i ran 'svn log foo bar'. If you have a good reason to
believe that most users will be looking for that information, then
i guess i'll just have to make a zsh function svnlog that does what
i want.

But i don't think that's what people want; it doesn't sound
particularly useful. I think when people give multiple files to
svn log, they want to see the history of each of those files.

> + once -- that is, if both FILE_A and FILE_B changed in that revision,
> + it won't be printed twice, only once.

I think it should be, but in separate sections; i want to see the
full history of each file that i listed.

+ If you need the (possibly intersecting) sets of revisions printed
> + separately, run the command twice, once for each file.

I'll do this if you really believe people want to ask your question
more than they want to ask mine.

Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 21 06:15:36 2002

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.