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

Re: issue with relative externals after a rename

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Wed, 28 Mar 2018 12:18:34 -0400

On Wed, Mar 28, 2018 at 10:59 AM, Nico Kadel-Garcia <nkadel_at_gmail.com>

> On Wed, Mar 28, 2018 at 10:36 AM, Nathan Hartman
> <hartman.nathan_at_gmail.com> wrote:
> > Our requirements are: at any time in the future, if someone checks
> > out code from the past, they should get exactly the same tree as what
> > existed in the past. I assume that this is probably THE #1 use case
> > and desired behavior for externals. Is that correct? If not, is there
> > a good reason to want otherwise?
> Then make tags. Tags need to be locked down, with no commits permitted
> on top of the tag.


> > (3) ^/SVN/path/to/project/tags/specific_tag@[number]
> >
> > Subversion first goes back in time to that revision, then goes to
> > that path.
> >
> > This is where I'm a bit foggy: Once it goes back in time and goes
> > to that path, does it then follow it forward to HEAD? Or does it
> > stay in the past?
> >
> > We've set up all of our externals like (3)... Do we need to go
> > through our repo and change all externals to specify both the peg
> > and operative revision?
> If you're permitting commits on top of tags, probably so.


Right now tags are not locked down. Perhaps they should be. But we
will begin with specifying both the peg and operative revisions and
then go from there.

Thank you for your input. Thanks also to Branko and thanks to the
OP for asking the original question, without which we would not have
discovered this about our repo until after things broke later on. :-)
Received on 2018-03-28 18:18:40 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.