[darcs-users] renaming the rerecord command

[Erik Schnetter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 19 October 2004 11:42, David Roundy wrote:
> On Mon, Oct 18, 2004 at 06:20:10PM +0000, Mark Stosberg wrote:
> > On 2004-10-18, Tommy Pettersson <ptp at lysator.liu.se> wrote:
> > > To rename it to 'update' could cause confusion with the very
> > > different cvs command.  I suggests 'amend' if it should be
> > > renamed.  'rerecord' makes you think of it as a 'record', but
> > > since it is a "dangerous" command, it might be better to think of
> > > it as an amendment.  What do others think?

Make it non-dangerous?  Remember whether the patch has ever left the 
local system?  Create a new inode?  Allow people to change the patch 
name (and everything else, e.g. drop hunks etc.) during rerecording?  
Make rerecord equivalent to unrecord and record?

> Since it's quite a new command, I'm amenable to changing it's name
> even this close to 1.0.0, but would like a bit more discussion, in
> case other people find "amend" confusing, or like "rerecord".

For those of us who do not speak English as native language, each such 
special word has to be learnt anew.  For us, rerecord is easier than 
amend.  On the other hand, if the darcs interface becomes richer and 
richer, then in the end we'll want a graphical tool for the 
inexperienced anyway.

- -erik

- -- 
Erik Schnetter <schnetter at aei.mpg.de>   http://www.aei.mpg.de/~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBdOS5m3uiSwno3f0RAoCpAKDCAWvQvFdIn6KpTT3YsnTues8HMwCfZYS/
rpxsY5Fg1hEz4YvVN+GkwYE=
=rJrp
-----END PGP SIGNATURE-----