After checking in the cvs NEWS file, the "commitid" feature was introduced
in cvs 1.12.12. This is a port of a cvsNT feature.
Another thing a bit off-topic: the main reason reported by people not using
tailor in the git community is the lack of branch support. I think it is
quite easy to implement branch support in the git backend to the level of
the cvs backend, but that will not be sufficient.
I'll experiment this week-end if I find some time with a quite simple idea:
adding a couple of parameters to the git backend to tell where to find a
trunk to graft the branch onto, and at which point to graft it. That will
still not be optimal, since mirroring a repo with all its branches will
require one mixed cvs-git repo for each branch, and they will all need to
be declared in the config file - multiplied by 2 for 2-way gateways. But
still, that should provide a reasonable support for branches.
|---------+------------------------------>
| | Yann DIRSON |
| | |
| | 29/05/2006 15:32 |
| | |
|---------+------------------------------>
>------------------------------------------------------------------------------------------------------------------|
|
|
| Pour : Lele Gaifax <[EMAIL PROTECTED]>
|
| cc : "[email protected]" <[email protected]>, [EMAIL
PROTECTED] |
| Objet : Re: tailor error (cvs->git)(Document link: Yann DIRSON)
|
>------------------------------------------------------------------------------------------------------------------|
The CVS repo is not public, sorry. Yes, it was a single commit (a merge
result), involving a large number of files scattered in dozens of dirs,
involving a good number of huge binary files. It really took several
minutes to complete.
Here is an example log entry including commitid. I have not dig very far,
but I've noticed it is consistent among all files that are part of a single
commit command, even when scattered in several dirs. So I infer it is
generated by the cvs client, and I suppose it needs server-side support as
well. I'm using 1.12.12 on both sides.
----------------------------
revision 1.9.2.2.2.1
date: 2006-05-24 09:51:07 +0200; author: ydirson; state: Exp; lines: +6
-5; commitid: 4371447410614567;
Fusion des modifs de build
=============================================================================
While I think of it : I cannot find a comment syntax documented in the doc,
altough '#' seems to work.
It may be worth mentionning that an empty repository section is OK, maybe
because it is inheriting things from DEFAULT - I end up having empty
[git:*] sections, since the by-default-added "repository" attribute is
useless.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
