[Savannah-cvs] [SavaneSvkBranch] (edit) Change introduction: this is not used anymore, this is a sample documentation

[Beuc]

??changed:
-We need to track a couple Savane changes specific to Savannah, such as the 
local configure.cache configuration, favicon.ico, keeping the FAQ around, plus 
the magic number anti-spam trick.
-
-I suggest we do so by creating a local SVK branch and keep sync-ing with it.
We needed to track a couple Savane changes specific to Savannah, such as the 
local configure.cache configuration, favicon.ico, keeping the FAQ around, plus 
the magic number anti-spam trick.

We did so by creating a local SVK branch and keep sync-ing with it.

++added:
Here's how we did it in 2006. At the time I was globally dissatisfied because 
SVK is slow, I had troubles getting my branching done (but maybe my branching 
scheme wasn't clean), the lack of answer when submitting detailed bug reports 
to the mailing list, and the fact I irremediably messed my local SVK repository 
a couple times. This may have changed since then with SVK2. It's still nice to 
be able to remotely clone and use a SVN repository.



--
forwarded from 
https://savannah.gnu.org/maintenance/address@hidden://savannah.gnu.org/maintenance