Gerhard Fiedler wrote:
> Timothy J. Weber wrote:
> 
>> Indeed.  Sounds like culture.  :)
> 
> Version control is culture -- programming culture :)

Agreed.  Now, can we somehow define all culture as version control??

> Apparently svn has come quite some ways since I last looked at it. It seems
> that most of my "must have"s and "want have"s are there now -- but of
> course that's by far not enough to switch :)

Of course!  If it's only as-good-as what you're using now that would be 
a lot of time and effort for not much reward.

>> I guess I never spend significant time out on branches... I wonder why.
> 
> My experience is that there is a bit of an entry hurdle to branching, and
> most people only make the step when they have to. At least that was the
> case with me. But ever since, I'm using it quite a bit; it's a very useful
> tool. How often do you want to just try something out? Put it on a branch,
> and even if you don't use it now, it's there, for later use. Or the typical
> case: I have a stable branch for a firmware and a board that's out in a
> product. I'm working on an updated board, and there are some changes to the
> firmware related to the new board -- but that board is not yet in
> production. In the meantime, the client wants some changes to the
> production firmware. With branches, that works nicely in parallel and comes
> all together when the time is ripe.

I do use them in both those ways... just not very often.  Maybe I still 
have the scars from the old sccs days when version control was 
coal-fired and branching required actual twigs as part of the incantation...
-- 
Timothy J. Weber
http://timothyweber.org
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist