Re: [Gnu-arch-users] Selected files commit

[Miles Bader]

On Sat, May 01, 2004 at 01:38:53AM +0200, Matthieu Moy wrote:
> With arch, you're encourraged to
> 
> 1) tla make-log
> 2) do some modifications -- Edit the log file while you are doing them
> 3) tla commit
> 
> (The tutorial, for example, says: "Whenever you create a new revision,
> the first step is to create a log file for that revision")

Hmmm.  I've certainly never done it that way (and don't want to).  It's
important to distinguish between the tutorial saying to do something, and
people actually doing it.  :-)

I think the tutorial -- and some tla commands/features -- are sometimes
rather out of sync with actual user practice; in some cases it's because the
users are lazy bozos (er, just talking about myself here :-), but in others,
the ideas described simply didn't work out.

So, is there anyone out there that actually _does_ do it the `tutoral way'?

I find that with arch, I often just make much more frequent commits, to the
point where there's little point to maintaining a log file as I go -- it's
just easier to write the log entry at the point of commit, as everything's
still fresh in my mind anyway (and as Stefan mentioned, it can make the log
entry more accurate).

Sometimes I'll do a `hack on lots of little bits' session, and then finally
use selected-file-commit to commit a bunch of changes a once.  In this case,
I want a separate log file for each changeset anyway, and once again it's
often easier to just them it at the point of commit.

[I think maybe the moral here is `document early and document often -- but
 not _too_ early/often.']

Thanks,

-Miles
-- 
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over.  --Ian Wolff