Bug: bea/520

ID :	52034fd0-ec50-424d-b25d-2beaf2d2c317
Short name :	bea/520
Status :	open
Severity :	wishlist
Assigned :
Reporter :	Martin F Krafft <madduck@debian.org>
Creator :	W. Trevor King <wking@drexel.edu>
Created :	Fri, 24 Jul 2009 12:04:08 +0000
Summary :	Allow autocommit option for command line interface?

Comment:

--------- Comment ---------
ID: b17a561a-6100-490e-84eb-d1ae4b617940
Short name: bea/520/b17
From: Martin F Krafft <madduck@debian.org>
Date: Fri, 24 Jul 2009 12:09:02 +0000

...
Also, why doesn't be commit after it takes an action? I think it's
kinda weird that I have to commit after creating a new bug.
...

as posted in
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477125
  on
    Fri, 12 Jun 2009 17:03:02 +0200

Comment:

--------- Comment ---------
ID: 4c50ca0b-a08f-4723-b00d-4bf342cf86b6
Short name: bea/520/4c5
From: W. Trevor King <wking@drexel.edu>
Date: Fri, 24 Jul 2009 12:33:58 +0000

I'm all for flexibility, so long as it doesn't require too much
hackery to implement it.  You'll have two problems:

  * Determining what to commit.

    You'd have to have RCS keep a log of all versioned files it
    touched, and extend .commit() to accept the keyword list "files"
    and commit only those files.  This is doable, but maybe not worth
    the trouble.

  * Generating meaningful commit messages.

    You'd have to add this functionality to each command (and future
    commands).

This would probably not be a good idea for the Arch and Mercurial
backends, since they have a limited ability to rewrite history when
you screw up your commit message (as far as I can tell).  Mercurial
does have "hg rollback", but it only works once, and lots of
typo-correction commits would just make the logs awkward.

Comment:

--------- Comment ---------
ID: 79fb6ef2-176c-45c0-b898-59c3c3e0aafe
Short name: bea/520/79f
From: W. Trevor King <wking@drexel.edu>
Date: Sun, 06 Dec 2009 21:45:15 +0000

>   * Determining what to commit.
> 
>     You'd have to have RCS keep a log of all versioned files it
>     touched, and extend .commit() to accept the keyword list "files"
>     and commit only those files.  This is doable, but maybe not worth
>     the trouble.

On the other hand, just attemting to commit everything after each
command would make it nice and easy to commit bug fixes:
  be --auto-commit status XYZ fixed
which would commit whatever changes you had outstanding with an
appropriate commit message.