Re: [Monotone-devel] automate get_current_revision [was --non-interactive ... ]

[Zbigniew Zagórski]

31-01-08, Zbigniew Zagórski <address@hidden> napisał(a):
> Thomas Keller wrote:
> ...
>  >
>  > On a related note, if you think of doing commits over automate like
>  > I currently do, what is really _lacking_ in automate is a way to
> let > mtn
>  > return a valid restricted revision for a given set of paths (i.e. I
>  > currently just feed put_revision with the complete output of
>  > get_revision). One could of course do the node restriction logic in
>  > the client (f.e. for renames), but this is very ugly.
>
> How about adding:
>
>         automate get_current_revision [PATHS...]
>
> Which will return current workspace revision restricted with PATHS.
> Now when automate commands can accept options it will be possible to
> add --depth and --exclude options also.

Hi,

I've commited f6cb000f1bbcf35e6458c5e62e10ecef02021752 with
implementation of this command. Please review if worried about quality
;) (tests/doc/NEWS).

Best regards,
-- 
Zbigniew Zagórski
/ software developer / geek / happy daddy /

get_current_revision.patch
Description: Text Data