Varnau, Steve (Seaquest R&D hp.com> writes:
> > -Original Message-
[...]
> > From: Stefan Sperling [mailto:stsp elego.de]
> > The easiest thing to do is to just leave the mergeinfo alone and upgrade
> > all clients to 1.7. This will get rid of superfluous mergeinfo
> > modifications durin
On Wed, Sep 19, 2012 at 05:55:27PM +0200, Michael T wrote:
> Stefan, thanks for your reply. Would a clean-up like I described (gathering
> changesets from all mergeinfo from all subtrees within a branch and setting it
> all on the branch root) be even theoretically correct then, or am I being
>
> -Original Message-
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: Wednesday, September 19, 2012 6:26 AM
> To: Michael T
> Cc: users@subversion.apache.org
> Subject: Re: Subtree mergeinfo
>
> On Wed, Sep 19, 2012 at 01:12:50PM +, Michael T wrote:
>
Stefan Sperling elego.de> writes:
> On Wed, Sep 19, 2012 at 01:12:50PM +, Michael T wrote:
[...]
> > We have a large project with multiple branches versioned with Subversion
> > (most
> > of us are using 1.6 clients at the moment). There is a lot of merging done
> > between branches, and it
On Wed, Sep 19, 2012 at 01:12:50PM +, Michael T wrote:
> Hello,
>
> I am aware that this is a much asked question, but since I have nonetheless
> been
> unable to find an answer which quite works for me I will ask it again. Feel
> free to point me to a FAQ I have missed by way of answer if a
