> On 30.03.2012 15:01, Simon Large wrote:
> > On 30 March 2012 13:55, Jean-Marc van Leerdam<j dot m dot van dot leerdam at gmail dot com> wrote:
> >> Hi,
> >> On 30 March 2012 13:59, Stefan Küng<tortoisesvn at gmail dot com> wrote:
> >>> On 30.03.2012 13:56, Tobias Richter wrote:
> >>>> Hi *,
> >>>> if I use the "Update to revision" my local working copy is updated to
> >>>> revision x but all the externals are still coming from the head
> >>>> revision or the explicit revision which was set through the properties.
> >>>> My suggestion: an option that I also get the externals from the revision
> >>>> x ...
> >>> So you mean if I want to update my TSVN working copy to e.g. revision
> >>> 22700 then all the externals (subversion, apr, neon, ...) it uses should
> >>> also update to that revision?
> >> I think the OP means that the externals are to be updated to a revision that
> >> was appropriate at the time rev. 22700 was created; he did not mean to reuse
> >> the 22700 as a rev no for the externals.
> >> Now, that info is probably not available for externals that were not linked
> >> to an explicit revision at that time, but for fixed externals it could be
> >> possible. The question remains if this is a feasible option to provide and
> >> if it requires additional SVN support to implement this.
> >> IIRC, there is an option when tagging/branching to freeze externals pointing
> >> to HEAD to a fixed revision? Maybe the OP can use that to achieve his goal?
> > That is exactly what you have to do when branching/tagging, and when
> > using an external repository. And that is what our docs recommend.
> > However there is another use case where you are using externals as a
> > convenience to reference some other part of your own repository, for
> > example a common library. In that case for trunk development you would
> > normally be working with the HEAD revision for both project and
> > externals. If you then want to go back in time perhaps to track down
> > when a bug was introduced, you would want both project and externals
> > to go back to the same earlier revision.
> And that's maybe convenient, but dangerous and should be avoided.
> Because if the external is changed (e.g. a bug fix) it is possible that
> this change breaks the build for that project. Or introduces some other
> problems. If you link always to head of such a "moving target" then you
> can easily break something.
> > So maybe what the OP wants is an option to update any externals which
> > are in the same repository to be at the specified revision.
> While I understand the reasons for this, there are several reasons I
> won't do anything here:
> * first of all, updating is done in the svn library. Which means this
> must be done in the svn library and can not be done in TSVN.
> * second: as I already said this situation is bad by design.
> Implementing something like this would just encourage this bad design
Sometimes we don't have control over the organization of the projects we work on.
I'm currently working on a project with several unpegged externals.
Today I'm working on a bug where I'd love to be able to pin down the revision that introduced it.
It would be really nice to have an option to update externals to the date & time of the revision selected in 'Update to revision'.
I understand Subversion doesn't have this option but it seems fairly easy to implement. I guess I'll write a script to do it for me. I so much prefer the Tortoise GUI and a checkbox would be nice...
Thanks for all you've done,
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-10-23 22:44:12 CEST