26 Sep
2005
26 Sep
'05
1:55 p.m.
On 9/26/05, Akim Demaille <akim(a)lrde.epita.fr> wrote:
Ok
Yes it's a good idea for a general vcs improvement but for this
problem of commits
I prefer this solution which do not break the old naming. Moreover
when conflicts you
can choose the one you want telling the specific name.
Best regards,
--
Nicolas Pouillard aka Ertai <ertai(a)feydakins.org>
http://uttk.org Uttk -- Unified Test Tool Kit
>>
"Nicolas" == Nicolas Pouillard <ertai(a)lrde.epita.fr> writes:
Index: vcs/NEWS
--- vcs/NEWS (revision 231)
+++ vcs/NEWS (working copy)
@@ -1,5 +1,15 @@
New in 0.4 ...:
+ * Vcs extensions files:
+ - Protocol version:
+ You can now add `protocol_version "0.1"' in your extensions.
Thus
+ you will be alert when the format will changes.
s/alert/warned/ s/will//
+ -
Default commit:
+ By adding `default_commit :your_commit_method' you override the
+ default commit method with yours. So you can call `commit' and `ci',
+ but also your old aliases. Of course you can call the real commit
+ with `commit_' or `ci_'.
I'm not sure that's the real feature one wants. What is desirable is
to built on top of the current method. This is very similar to using
the "super" method (or "Precursor" in Eiffel parlance).
This should be possible for all the commands.