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

RE: svn commit: rev 4391 - [...]

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2003-01-15 01:30:27 CET

I apologize for the huge commit mailer email, but there were a couple of
reasons I wanted to do it this way:

* Pretending to be a normal user.
* Fix those broken EOLs in some of the files on the branch that Greg
noticed when I last merged the changes in.

Clearly the commit emailer needs some help dealing with large commits.
The first merge email that the emailer wanted to send out, never came
out over the list. (r4324) I'm hoping that was simply due to the list
management software. I'll be logging an issue about the commit emailer,
and hopefully someone can fix it into generating more concise output
when the list of changes is so long.

Just as an FYI that commit took ~20 min. to run, and ate up >60MB of
memory. However, the commit was done with MSVC debug bits, and through a
proxy web server so the current ping time to svn.collab.net wasn't
known. The client svn process seemed to be more I/O limited than


> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> rassilon@tigris.org writes:
> > Author: rassilon
> > Date: 2003-01-14 17:35:39 -0600 (Tue, 14 Jan 2003)
> > New Revision: 4391
> >
> > Added:
> > branches/issue-1003-dev/packages/win32-innosetup/svn.url
> > branches/issue-1003-dev/packages/win32-innosetup/svn_isx.pas
> > [...]
> Bill, any reason you don't make your changes in the one
> subdirectory of the branch (libsvn_fs), and keep that
> directory `switch'ed in your working copy? That way you're
> always on trunk except for your changes, and people on slow
> links don't have to deal with huge merge mails every now and then.
> -Karl

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 15 01:32:05 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.