Hmm.. It seems that that is a feature of SVN's atomic commits. A commit of 1,000 files is a single unit, and not 1,000 single-files commits as it would be with CVS. So the log of 1 file would show everything that happened in each revision it got changed in. Checkin-comments describe the whole checkin, and not changes per-file.
Well, let's hope that issue 1093 gets fixed soon, if this leads to large inconveniences for you and your team!
regards,
--Tim
> -----Original Message-----
> From: Attila BODY [mailto:compi-lists@freemail.hu]
> Sent: maandag 29 maart 2004 9:33
> To: Leeuw van der, Tim
> Cc: users@subversion.tigris.org; sussman@collab.net
> Subject: RE: Re: Bug#1093 makes move/rename feature almost useless
>
>
> On Fri, 2004-03-26 at 15:17, Leeuw van der, Tim wrote:
> > > Well, I have to disagree here with you. svn log -v throws me
> > > every change
> > > in the wole repository, not only the hostory of the
> specified file. It
> > [...]
> >
> > But yo can do
> >
> > svn log -v <filename-goes-here.file>
> >
> > And that should give you the history of just that file. If
> *that* doesn't work, then you've got another bug....
> >
> I seems I did...
>
> svn log -v <targetfile> logs only revisions where the <targetfile> has
> been changed but logs everything what has been changed in that
> revisions, not only <targetfile> This way you may end geting thousands
> of lines logged. And try to force your windoze devels to use grep ;)
>
> thanks,
>
> Atila
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 29 09:39:40 2004