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

Re: svnmerge.py Policy (Was: Re: svn commit: r21294 - in branches/ebcdic/v5r4/1.4.x...)

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-09-02 01:04:24 CEST

On Mon, 28 Aug 2006, Justin Erenkrantz wrote:

> On 8/28/06, Paul Burba <paulb@softlanding.com> wrote:
> >I looked at using svnmerge.py for this merge, recalling a few posts
> >mentioning it. But after finding little in the way of guidance on how to
> >use it on an existing branch that's been merged into repeatedly already, I
> >turned my attention to other things. I did this somewhat out of
> >frustration but mostly because I was unaware it was required...
> As I've said before, those people who want us to use svnmerge.py
> everywhere need to commit some instructions somewhere into HACKING.
> Ideally, example snippets should also be included in STATUS or
> whatever. But, forcing people to play hunt the wumpus to merge is
> silly. -- justin

Why not require its use only for release branches? It's already setup
for all such branches...

  • application/pgp-signature attachment: stored
Received on Sat Sep 2 01:03:13 2006

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.