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

Re: Branches and tags

From: Frank Gruman <fgatwork_at_verizon.net>
Date: 2005-06-03 19:30:18 CEST

Yes - a cookbook of sorts. The thing I would stress in this case is
that it truly be a 'best practices' type of guide from those who really
know what Subversion was meant to do. An intelligent person (_BIG_
assumption here) could take those variations and apply them. My concern
would be that you end up with input from 1000 others, many of whom deem
a 'best practice' something that is really only 'best' in their
particular scenario.

The forums are a great tool to glean a little information about how
everyone else is using the system, but for an introductory tool, I think
a compiled list of "How-To's" based on 3 or 4 different use scenarios
would be great.

Regards,
Frank

Ben Collins-Sussman wrote:

>
> On Jun 3, 2005, at 7:38 AM, Frank Gruman wrote:
>
>>
>> So - to end my large essay, I think that a helpful document addition
>> could be a series of examples in different scenarios (pick two or
>> three scenarios, and build on them chapter by chapter).
>
>
> Ah, interesting! Sort of a companion "cookbook" with best practices,
> eh?
>
> There are now several SVN books out there now, and I suspect at least
> one of them is more cookbook-like, rather than more reference-like.
> (Like Garrett Rooney's book.)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 19:35:01 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.