[Monotone-devel] Re: Monotone revert

[Bruce Stephens]

Daniel Carosone <address@hidden> writes:

> On Mon, Dec 12, 2005 at 08:24:18AM -0300, Alex Queiroz wrote:
>> Hallo,
>> 
>>      'Monotone revert' without arguments reverts the whole directory.
>
> and worse, does so silently. It should describe its changes (like
> update does).

So you can watch it as it destroys your changes?

>> Isn't that dangerous? I like the subversion way that requires an
>> explict dot: 'subversion revert .'. What do you think?
>
> That seems like a good idea, actually.

Alternatively, it could save the differences.  As an example, GNU Arch
does this when you do "tla undo": it creates a patch which you can
later redo.

So "monotone revert" could do the equivalent of "monotone diff >
MT/revert.<n>", "monotone revert", or something like that.  Probably
with an option not to save the changes.  And maybe it would name the
file in some more useful way, maybe by date or something.  

And we'd want a "monotone patch", but we probably want one of those
anyway.  I guess it makes most sense to wait for rosters before
working on that, now.

All of that seems nearly what some other systems have with "shelves"
or quilt-like functionality.

I can imagine other ways of implementing something similar (it could
commit the whole revision without a branch cert, for example, before
reverting the working copy).  I don't know which would offer a
coherent model overall, though.