[Monotone-devel] Some smaller issues, Nico's TODO

[Nico -telmich- Schottelius]

Hello everybody!

Some issues I am not sure of:


1. Should "rename" not really be "move"?
   Summary speaks about a move, I think about a move,
   but monotone uses "rename". Somehow not intuitiv.

----- rename-snip -----
scice% monotone rename indent_script scripts/indent_script 
monotone: adding indent_script -> scripts/indent_script to working copy
rename set
scice% monotone status                                    
Old manifest: 3dfbfcc24ea13711795065c0c54c993c430f3ac3
New manifest: b44f1c9ef066f8612d4944d06e710139e296e675
Summary of changes:

  move indent_script
    to scripts/indent_script
----- snap -----

2. Can we change the output of the certs command?
   I think the "old" way is rather hard to read.
   Instead of

------------ snip ---------
Key   : address@hidden
Sig   : ok
Name  : author
Value : address@hidden
------------ snap ---------

I would suggest

------------ snip ---------
Key   : address@hidden [SIG: ok]
Author: address@hidden
------------ snap ---------

3. When adding a directory (like scripts) with monotone
   add and there is a file already scheduled for something
   else monotone gives an error:

------------ snip ---------
scice% monotone add scripts 
monotone: adding scripts/monotone-snapshotting to working copy add set
monotone: misuse: adding file scripts/indent_script, also scheduled for
target of rename
------------ snap ---------

   IMHO monotone should print a warning and ignore the already
   scheduled file.

4. When using monotone log / commit I would like to include
   the changes made by monotone:

------------ snip ---------
MT:   move indent_script
MT:     to scripts/indent_script
------------ snap ---------

   What do you think of including the lines into the output of
   log?

Just some thoughts,

Nico

pgphJ4riUV1z4.pgp
Description: PGP signature