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

Re: cvs2svn: raw or cooked?

From: Jim Blandy <jimb_at_savonarola.red-bean.com>
Date: 2000-09-25 21:33:53 CEST

Karl Fogel <kfogel@galois.collab.net> writes:

> Jim Blandy <jimb@savonarola.red-bean.com> writes:
> > 2) Sort all those entries by commit time, preserving the filename,
> > revision, and log entry.
>
> Agree with Jim's algorithm. Don't forget to inculde the commit's
> author in the above list of properties, too. (I'm sure the omission
> was accidental, I just wanted to mention it for completeness.)

Hadn't thought of that. Clearly that's correct.

> > commits that don't belong together. It should probably ignore
> > whitespace differences, etc. Cvs2cl has logic for this that people
> > like.
>
> Actually, cvs2cl doesn't ignore whitespace differences in the log
> messages when discovering commits, nor (IMHO) should cvs2svn, since
> there's no way for the log message to differ by whitespace (or by
> anything else) within a single commit.

That's reasonable. I guess I was thinking about cases where one does
several commits with `identical' log messages by hand. In that case,
the spacing might get a little screwed up, but it still looks like one
commit. I'm not positive that kind of fuzz is a good idea, though.
Anyway, if someone finds it useful, it's easy enough to add.
Received on Sat Oct 21 14:36:09 2006

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