Re: [Gnu-arch-users] Re: give us a hand with arch

[Stephen J. Turnbull]

>>>>> "Dustin" == Dustin Sallings <address@hidden> writes:

    Dustin>     I usually don't do any logging before a commit.  It'd
    Dustin> be nice to be able to do perforce/cvs style commits with
    Dustin> notes, I think.  Of course, if in the end, we only have
    Dustin> one model, I like the one we have.

What I'm working toward (slowly) is a model in which "arch commits"
are almost as lightweight as a file save.  The additional effort
involves a single keystroke selection from a small number of keywords
(I have typofix, bugfix, comment, ontask in mind).  Then as the
changes build up, arch starts to nag you to organize your commits.

"Organize" means to commit larger changesets to a "clean" branch.  So
arch will present you with a set of "typofix" patches, you review, if
you like, you say "go" and arch replays those into the clean branch,
then commits with a single log.

The big problem here is that there needs to be support for slicing and
dicing changesets (suppose you commit a couple of typo hunks in an
largish "ontask" commit?).

I'm only going to support this in Emacs, but the general idea got mild
interest from Tom (as an alternative style), and active opposition
from Miles.  :-)

But it gives you some idea of the various kinds of things arch will
support.

    Dustin>     OpenCM does both in that you can edit your future
    Dustin> checkin message at any time up to the checkin (at which
    Dustin> point it will be presented to you for your final edit).

Arch does, too.

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.