Thanks for the feedback and as a fellow VSS convert, I appreciate your
concern and your willingness to pass along the knowledge gained from your
own conversion experience. I certainly meant you no personal offence. When
I mentioned the potential lack of understanding, I knew I ran the risk of
offending some members of the list that actually do have a firm
understanding of VSS. I didn't remember exactly who responded which way so
I'm afraid my response may have been overly generalized.
I'm beginning to settle into the SVN way and I do like it. Though I must
say the loss of the ability to diff against the HEAD of a repository is
still a bit of a pain for. Me, I know I can export the HEAD and Diff
against that, it's just inconvenient is all. But no product will ever have
the perfect combination of all the features someone might want. The
advantages of SVN certainly seem to far out way the few disadvantages when I
compare it VSS.
From: Jeff Smith [mailto:firstname.lastname@example.org]
Sent: Friday, March 30, 2007 1:54 PM
Cc: Tom Malia
Subject: Re: GUI Diff on Repository HEAD and "a" directory?
On Wednesday 21 March 2007 16:15, Tom Malia wrote:
> To everyone who keeps saying... "You're doing it wrong because you
> don't understand" I'd like to say... I've never said I wasn't
> "doing it wrong" I just said that this is how it's being done and
> that this is partly due to the structure of the product I've been
> using. As for me not "understanding" I would argue that I think I
> understand it pretty well, there actually seems to be some lack of
> understanding on the other side about how VSS works (though Ingo
Hi Tom, I hope you don't mind me posting one more note here. I really
do think the thread was confusing and others should not have spent so
much space trying to tell you that you didn't understand. I think you
underestimate, however, the amount of expertise of those who are
talking about VSS. I suspect they also have valid baggage from those
days ;-) But true, it still comes down to each group deciding their
own way to migrate... or not to migrate.
vvv Now to the point vvv
You asked if you could easily Diff the current work in Subversion with
a folder which is not a SVN WC (not a working copy from svn repos).
Yes, do this with a separate Diff tool. You talk about exporting from
SVN so you have a "pure filesystem" copy to use for Diff, but I don't
see why you need that step. The WC is certainly a copy of the files
you want to compare, already. Since you would use a third-party diff
tool, could that tool easily ignore the ".svn" subfolders? Those are
the only difference between a WC and the "pure filesystem" version.
> No matter how much you might say "you need to stop thinking in the
> 'old way' and see the light of the new religion" the fact is,
> first, that's simply not possible, we all bring all our baggage
If we all bring baggage, then why do you think your situation is
different? Most definitely changing religion IS possible, or
practically none of us could say it. Most all of us have converted
from something else because Subversion is so new. And yes, I did
"stop thinking in the 'old way' and see the light of the new
religion". I bare testimony that it is the most effective way to
For example when I try to remember the way both CVS and SVN work at
the same time, I get plain messed up. I understood each very well,
but not at the same time! Instead I only have to remember my work
flow. Often I have to be reminded that something in my workflow was
just a quirk to satisfy a specific version control system, and not
something I needed to be done. If I allow my developers to carry on
with that quirk when no longer necessary, I pay more than migration
costs. I lose workflow cost every day!
But nevermind that because you only need to do it during migration.
When it comes to sending off a package to a third-party for their
changes, you just need to understand "vendor branches", which is yet
another subject, and I think handled very well by SVN.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Apr 1 02:45:44 2007