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

Re: [Patch] cvs2svn.py

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-07-19 20:46:06 CEST

On Fri, Jul 19, 2002 at 03:16:51PM +0200, Sander Striker wrote:
> > From: Swen Thuemmler [mailto:swen@mediaways.net]
> > Sent: 19 July 2002 15:02
> > On Fri, Jul 19, 2002 at 03:05:33PM +0200, Sander Striker wrote:
> >
> > > Question: How do you determine if multiple commits are in the same
> > > changeset when their commit msg differs? I mean, mostly a cvs commit
> > > of multiple files will have the same commit msg. When are the commit
> > > msgs ever different _and_ still detectably in the same changeset?
> >
> > As I did understand, the changeset is identified by a time frame
> > (initially 5 minutes I think) and possibly by the author of the changes. I
> > I just noticed the missing log messages and tried to put them back.
> Odd, if this is happening, I'll deflect my question to Greg: why are
> commits with a different log msg identified as being in the same
> changeset?

*if* being the operative word. I cannot believe that we would be combining
things with different messages into a single commit. The identifying key is
a combination of the author and log message. A second use of that key must
occur within a five minute window to be combined into the commit with the
first use. The time lag is because the commits are not atomic -- they will
span periods of time, based on the speed of the user's connection and what
they are uploading/committing. When converting the mod_dav repository, the
commits have spanned no more than a few seconds.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 19 20:44:13 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.