Denis Barbier wrote:
On Mon, Feb 23, 2004 at 07:29:23PM -0500, Joey Hess wrote:
[...]
Failing that, your b) looks not too bad. One thing that makes it easier
is that due to svn's different versioning method, we only need to record
one number, the current revision of the whole repository
I have done a test import of d-i's cvs repository into subversion. The
repository is available for anyone who has commit access to d-i at
svn+ssh://svn.debian.org/svn/d-i/trunk or at
svn://svn.debian.org/d-i/trunk for anonymous access, and can also be
browsed with viewcvs at
On Mon, Feb 23, 2004 at 02:59:02PM -0500, Joey Hess wrote:
trunk/
tools/
cdebconf/
build/
branches/
d-i/
beta2
release
tools/
Bastian Blank wrote:
That looks better. I don't know why people love tags/ if they can use
more speaking directories.
Because I might want to tag something that is not a release. Also
because tags is in use in 99% of all subversion repositories out
there, and is in the documentation, and we
On Mon, Feb 23, 2004 at 02:59:02PM -0500, Joey Hess wrote:
I have done a test import of d-i's cvs repository into subversion. The
repository is available for anyone who has commit access to d-i at
svn+ssh://svn.debian.org/svn/d-i/trunk or at
svn://svn.debian.org/d-i/trunk for anonymous access,
Denis Barbier wrote:
Translated manuals rely on cvs revision numbers, as with boot-floppies,
so this change will be pretty painful here. I see 2 solutions:
a) Automatically replace cvs revision numbers of original files in
translated documents with svn revision numbers. Not sure if
On Mon, Feb 23, 2004 at 06:44:14PM -0500, Joey Hess wrote:
Denis Barbier wrote:
Translated manuals rely on cvs revision numbers, as with boot-floppies,
so this change will be pretty painful here. I see 2 solutions:
a) Automatically replace cvs revision numbers of original files in
Denis Barbier wrote:
On Mon, Feb 23, 2004 at 06:44:14PM -0500, Joey Hess wrote:
Denis Barbier wrote:
Translated manuals rely on cvs revision numbers, as with boot-floppies,
so this change will be pretty painful here. I see 2 solutions:
a) Automatically replace cvs revision numbers
On Mon, Feb 23, 2004 at 07:29:23PM -0500, Joey Hess wrote:
[...]
Failing that, your b) looks not too bad. One thing that makes it easier
is that due to svn's different versioning method, we only need to record
one number, the current revision of the whole repository after it is
switched to
9 matches
Mail list logo
