Re: [Gnu-arch-users] Re: file-limited commit on new file

[Stig Brautaset]

On Jan 02 2004, Miles wrote:
> one usually realizes the need to commit the new file _after_ adding it, so
> you really have to do something like:
> 
>    mv new-file.c ,new-file.c
>    tla undo
>    mv ,new-file.c new-file.c
>    tla commit ...
>    tla redo
> 
> which of course gets progressively more annoying if you have more than one
> new file.  Even worse, I find it's actually fairly to want to commit both a
> new file and a change to an existing file, and I'm not sure _how_ you'd
> handle that case with `undo'.

Actually, it's exactly the same. Think about it. :)

> Using undo for this case would be more tractable if undo itself permitted
> limits (and my personal favorite, limited excludes: undo everything _except_
> files x,y,z) -- including added/removed files.

Agreed, I'm very much for that improvement.

As an aside, it would be nice if 

 % tla commit -s"updated junk regex" -- {arch}/=tagging-method

worked... it doesn't with `explicit' tagging method, at least. tla
complains that the file doesn't exist in the ORIG tree. I'm not
sure if this is because it's missing an explicit (either in-file or 
separately) tag though.

Stig
-- 
brautaset.org