Re: svn commit: r17620 - in branches/svndiff1: . build/win32 contrib/client-side contrib/hook-scripts notes packages/rpm/redhat-7.x packages/rpm/redhat-8+ packages/rpm/rhel-3 packages/rpm/rhel-4 subversion/bindings/java/javahl/native subversion/bindings/java/javahl/src/org/tigris/subversion/javahl subversion/bindings/java/javahl/src/org/tigris/subversion/javahl/tests subversion/bindings/swig/perl/native/t subversion/clients subversion/include subversion/libsvn_fs_base subversion/libsvn_fs_fs subversion/libsvn_ra_dav subversion/libsvn_repos subversion/libsvn_subr subversion/libsvn_wc subversion/mod_dav_svn subversion/po subversion/svn subversion/svn/schema subversion/svnserve subversion/tests subversion/tests/clients subversion/tests/svn subversion/tests/svn/getopt_tests_data subversion/tests/svn/svntest tools/hook-scripts tools/test-scripts/svntest www

On Mon, 2005-12-05 at 21:57 +0000, Max Bowsher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Daniel Berlin wrote:
> > On Mon, 2005-12-05 at 12:34 -0600, kfogel@collab.net wrote:
> >
> >>dberlin@tigris.org writes:
> >>
> >>>Log:
> >>>Merge from trunk
> >>
> >>Say the revision range, to save future readers the effort of figuring
> >>out how up-to-date the branch is at a given moment?
> >
> >
> > I use svnmerge.py, so you can always tell by propget'ing the
> > svnmerge-integrated property.
> >
> > But i'll mention it in the future anyway.
>
>
> svnmerge.py writes a detailed log message for you!

>
> Why not use it?

Oh, i have that turned off by default because it takes forever on the
gcc sources (since it does it rev by rev in the version i've got. I
know Giovanni was going to go fix this). It usually took about 5x
longer than the actual merge :)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 5 23:05:24 2005