[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] new `tla changes --diffs' behavior
From: |
Tom Lord |
Subject: |
Re: [Gnu-arch-users] new `tla changes --diffs' behavior |
Date: |
Thu, 29 Jan 2004 09:51:07 -0800 (PST) |
> From: Charles Duffy <address@hidden>
> On Wed, 2004-01-28 at 18:05, Miles Bader wrote:
> > If the purpose of the output is interactive examination (which is the
case
> > the great majority of the time in my experience), seeing new file
contents
> > dumped is usually just (voluminous) noise -- at least for me, it's
almost
> > always enough to see the name of the new file.
> At the risk of worstening the s/n ratio, let me throw my hat in with
> Miles on this one. (No position on the one-flag-or-two bit, though)
>From the gatekeeper perspective, the opposite is true. At least the
way I'm currently working.
A merge goes something like this:
1) do the merge into my project tree
2) what-changed --diffs > +to-review
and then I review the merge, using "+to-review" to guide the process.
In that procedure, at least, I find the new-files output very useful.
(I don't, however, have any strong feelings about the default. I
wouldn't mind having to type an extra option name.)
-t