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

Re: SubWCRev: Options to recognize "tags" folder, "all externals set explicit" & more

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 24 Sep 2012 20:45:58 +0200

On 23.09.2012 19:35, Jan Linnenkohl wrote:
> Hello,
>
> in our projects we have the need to get some more information about
> the subversion status and I would like to generate a patch for this.
> I would like to present my ideas with this email and to discuss them,
> before starting the final work on the realization of it.
>
> Task 1 “tags”:
>
> I would like to get a new keyword substitution
> “$WCISTAGGED?TText:FText$”, which recognize the keyword “tags” in the
> repository URL. Optional this keyword should be set from the registry
> (same as in CSVNProgressDlg). I saw, that the implementation in
> “CSVNProgressDialog::IsComittingToTagTag” uses classes, which are not
> used in SubWCRev program. Can I use MFC or should I just add a
> command line switch (e.g. –tag=tags)?

SubWCRev does not use MFC at all. If you want to add something there,
you'd have to do it without it.

But instead of passing another command line switch, just read the
registry values.

> Task 2 “external use all explicit revisions”
>
> The second idea is to have another keyword
> “$WCEXTEXPREV?TText:FText$”, which recognize, if all used externals
> uses an explicit revision. This can be very helpful, to recognize, if
> there is an svn::externals, which uses the head revision instead of
> an explicit revision.

I suggest using $WCEXTISTAGGED or something like that. Not sure what
EXPREV would even mean.

> Task 3 “fixed externals lead not to mixed revisions”
>
> My last idea, would be to add a new command line switch “-E”, which
> works nearly in the same way as the current “-e” command line switch.
> The only problem with the current implementation is, that when an
> explicit revision for an external is used, we always get a mixed
> revision result. My idea would be, to ignore the externals with
> explicit revision, when the revision range inside of them is only the
> given explicit revision in the properties. So they would not lead to
> a smaller MinRev and so no mixed update revisions.

Seems ok.

> That’s my ideas and I would like to provide a patch for them. So
> please some feedback for my ideas!

If you want to provide a patch for this, don't forget to include methods
to get the same values for SubWCRevCOM.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3009857
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-09-24 20:46:07 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.