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

Re: locking externals

From: Neels Janosch Hofmeyr <neels_at_elego.de>
Date: Sat, 04 Apr 2009 02:21:17 +0200

Right, if no-one speaks up this time, I'll make two new issues.
~Neels

Neels Janosch Hofmeyr wrote:
> Hi,
>
> (Cc'ing TSVN because it's relevant to a mail on that list. This mail is
> mainly directed at dev_at_subversion)
>
> I'm investigating externals and found out that externals with a fixed
> revision aren't locked as long as that fixed revision == HEAD.
>
> While this may be a rare case for externals within the same repository, it
> could be more common with (dir-)externals coming from another repos. Then
> again, dir-externals need an explicit commit...
>
> Anyway, it's rare but still wrong, right? In my elaborate reproduction
> script (attached), this happens for both file- and dir-externals.
>
> On svn.haxx.se, I only found a reference that trusts a fixed revision to
> lock an external.
>
> Should I add an issue for this?
>
>
> Furthermore, I noticed that when I modify a fixed-revision external and
> update, the modifications get "merged", causing a conflict for some strange
> reason. Firstly, I think that conflict is probably erratic. Secondly, I'd
> say svn should at least warn that something considered uncommittable was
> modified, and maybe skip all "merge" attempts on a fixed revision external.
>
> Should I add an issue for this, too/either?
>
> ~Neels
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1475609
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1537328

Received on 2009-04-04 02:21:38 CEST

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.