Reinhard Brandstädter <reinhard.brandstaedter@ams-engineering.com> wrote
on 01/18/2005 09:29:35 AM:
> I was just playing around with the svn:externals properties and
subclipse.
> I was astonished when I did a commit to my whole trunk project in
> eclipse and the subdirectory with the svn:externals libraries was also
> commited to the external repository (on which I have write access).
> Just before I got a warning about a tag URL but later on I didn't
> receive this warning anymore (although answering NO).
> I replayed the same sitiation with TortoiseSVN which always brings up
> that warning and only allows a explicit commit on the
svn:externals-folder.
> Subclipse seems to commit straight through.
> (Version is 0.9.25 btw.)
>
> Is this a known Bug?
Why do you consider this a bug? When I originally tested this, I thought
it was a nice feature. Normally the complaint with svn:externals in
Subversion is that commit does not work well with it. The reason that
TSVN explicitly prevents the commit is that it does not work due to the
way they use the Subversion API's. The way Subclipse does commits it does
work.
I am not clear why we would want to prevent people from committing to
externals if we can do so correctly.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Jan 19 01:34:47 2005