Anna / Marek Latuskiewicz wrote:
> Well I'll be concise. I know that everyone praise the software he's
> writing but IMHO we need to patch 2 loopholes that are present and any
> ideas / initiative to patch it would be more than welcome. For the God
> sake we're on the same side - trying to get something for 0$ that is
> warth ClearCase + ClearQuest 10K$ each. Let reach some compromise or
> make people pay Rational...
> 1) Well the whole idea of BugzID - it's an excellent idea but the
> first loophole is here:
> If you use any operation with build-in commit like copy, rename - you
> need to work around it putting the bug into comment because there is no
> window for that like in simple commit. Adding such a window would be nice.
That's true, yes. If you do operations in the TSVN repository browser,
you won't see the bugzID edit box when you enter the commit message.
But seriously: can you close an issue by simply copying/moving
> 2) Checking out and in every directory, then every subdirectory..
> then do it again if you create any directory. don't you think this is
> over the top? Especially when you'd like to add this feature to a new
> repository so you need to check-out and in EVERY folder in EVRY branch
> to do that? I'm happy with the present implementation if you give me the
> way not to do it. I can see that binding these with properties has
> several pros.
As I already said: it's not perfect. But it's the best we can do right
now, as long as Subversion doesn't provide the means we need to make it
And I really don't understand your problem here:
Why do you need to check out every directory, *then* every
subdirectory?? You already have a working copy - just apply the
properties there and commit.
If you then start working on a new branch, you have to check out a
working copy anyway - so just apply the properties then.
> I can imagine situation in near future - The ideal situation -
> Inherited properties implemented in subversion and we can set it the
> root of repository without checking out it. Do you have any real life
> work around for now?
Yes, the way we do it now. That's our work around for this missing feature.
> You have to admit that adding this parameter to each subdirectory in
> each trunk & branch & label is well even impossible if I have 100 labels
> + 20 branches for a project that has 500MB of source code. or maybe it
> is possible - have you seen any working pre-commit/post-commit script
> with that? I'm not arguing anymore if you have such a script :)
> Otherwise ideas how to patch it are more than welcome.
Why do you need to add those to e.g. tags? Those are by definition
immutable (i.e. should not be changed anymore). So adding those
properties is not something you have to do.
And you can add the properties to all the branches you have when you
actually *work* on those branches, i.e. if you have a working copy
checked out from there.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 20 09:09:32 2006