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

Revert or update to Issue 285: externals: prevent commit of pegged externals?

From: <dlellis_at_rockwellcollins.com>
Date: Fri, 9 Aug 2013 15:33:51 -0700

Hi all,

Issue 285 was added to prevent a commit when an external had a pegged
revision (only allowed for HEAD).

I believe we should allow commits when the peg revision is the same as the
HEAD revision. I'm ok with preventing commits to pegged revisions that
are not the same as the HEAD. This makes some sense, although seems a
little bit over-protective.

Externals are used in our case to manage shared code between many
projects. Requiring users to have a checkout of each of the shared code
areas (of which there may be _many_) is unreasonable as is asking users to
unpeg their revision prior to committing a change to the shared code base.
 We have some automated tools for managing externals that this is causing
serious issues with.

If we can't add an exception to allow commits to files, can we add a force
command to allow a knowledgeable user to perform the action as requested?

We use some automated tools to help use manage the externals and this is
throwing a pretty serious wrench into the gears. This also discourages
our folks from contributing shared code as it means more work. Its hard
enough to encourage sharing of code the way it is!

Thanks in advance,


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-10 00:35:03 CEST

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

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