"Ben Collins-Sussman" <[EMAIL PROTECTED]> writes:

| On 28 Nov 2006 23:16:38 +0100, Gabriel Dos Reis
| <[EMAIL PROTECTED]> wrote:
| > "Page, Bill" <[EMAIL PROTECTED]> writes:
| >
| > [...]
| >
| > | Up to revision 199 (October 26), the 'svk smerge' transactions from
| > | the axiom-developer.org server that are intended to synchronize the
| > | Google repository with the SourceForge repository were properly
| > | processed by Google. For reasons that I don't understand, the svk
| > | smerge process did not automatically create the correct branch
| > | structure at Google when we created 'silver' on SVN SourceForge.
| >
| > I believe 'silver' was created from "scratch", so has not ancestry in
| > common with any other branch in the repository -- if my understand of
| > your famous picture is correct.  It effectively is a
| > "repository" within the repository  -- essentially, files are
| > _duplicated_ as opposed to being shared.  For me, that explains the
| > sudden surge.
| >
| 
| Yep, that would explain it.  Branches are supposed to be cheap copies;
|  they're just a hardlink within the repository, so they're nearly
| instantaneous to create and take essentially zero space when they're
| first made.  I don't know what you did on sourceforge, but it sure
| wasn't a normal subversion branch!
| 
| I can reset the google repository to revision 0 if you'd like.

That would be very much appreciated.

Bill, before your mirror to the next new repo, please let me make sure
that we don't store gcl and noweb as .tar.gz anymore.

-- Gaby


_______________________________________________
Axiom-developer mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/axiom-developer

Reply via email to