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

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

From: Paul Burba <paulb_at_softlanding.com>
Date: 2006-08-28 20:39:40 CEST

"C. Michael Pilato" <cmpilato@collab.net> wrote on 08/28/2006 02:04:33 PM:

> Kamesh Jayachandran wrote:
> > pburba@tigris.org wrote:
> >> Author: pburba
> >> Date: Mon Aug 28 06:57:49 2006
> >> New Revision: 21294
> >>
> >> Log:
> >> Merge r20780:21228 from branches/1.4.x to branches/ebcdic/V5R4/1.4.x.
> >>
> >>
> > Should we not use svnmerge.py to record merges?

Hi All,

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...
> I believe this is (and should be) a policy applied at a given branch
> owner's discretion.

...So what is our policy exactly? There is no mention of it in HACKING,
should there be?

Paul B.
> --
> C. Michael Pilato <cmpilato@collab.net>
> CollabNet <> www.collab.net <> Distributed Development On Demand
> [attachment "signature.asc" deleted by Paul Burba/SoftLanding Systems]

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 28 20:40:26 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.