output from 'bzr rm' should be more verbose and intuitive

[Marius Kruger]

I am planning to do the 'more logging' and the 'actually remove files' in
one bundle.

On 2/8/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
>
> Lukáš Lalinský wrote:
> > 'bzr rm' currently doesn't print anything by default:
> >
> > $ bzr add a.txt
> > added a.txt
> > $ bzr rm a.txt
>
> ...
>
> >
> > In 'bzr status' ? means that the file is not versioned, does is mean
> > here that the file is not versioned and so can't be removed? I would
> > personally expect that 'bzr rm' prints status of the file *during* the
> > remove, not after it. Or even better it could print the action, like
> > 'bzr add'. What about changing it to this?
> >
> > $ bzr add a.txt
> > added a.txt
> > $ bzr rm a.txt
> > removed a.txt
> > $
> >
> > -Lukáš
>
> Seems reasonable and nicely symmetric with 'bzr add'. We may want a 'bzr
> rm -q', since we have 'bzr add -q' to not report everything that goes
> on. Basically it just means enabling/disabling reporting based on what
> bzrlib.trace.is_quiet() returns.
>
>
> Also, I think someone was trying to change 'bzr rm' so that it would
> actually delete the file (versus bzr remove to only mark it as no longer
> versioned).
>
> You may want to coordinate on it, since you are likely to be working in
> the same area.
>
> John
> =:->
>
>


-- 



I code therefore I am.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070208/576106b9/attachment.htm