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

[Thomas Keller]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zbigniew Zagórski schrieb:
> 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,

Heh... I totally forgot about that thread, and that there is already an
implementation for get_current_revision sitting in
nvm.automate_current_revision (for quite some time) - but this is not a
problem. I'll review your version and we'll take just that. If
everything is ok, I'll suspend the old branch.

Thomas.

- --
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFHu+8aaf7NlBYNEJIRAlnYAJ9XjdyKAFtY2HHHF9aDgOId8F17dQCg5wf7
+kYpogC3yRTV1egjNPtJXS8=
=BUGR
-----END PGP SIGNATURE-----