[Monotone-devel] There's something FISHY with the latest code...

[Richard Levitte - VMS Whacker]

Hello,

It seems like the new code that was merged in last night (swedish
time) has a weird concept of what the current revision id is *when no
changes have been made*!

My workspace is currently at ce577c763adf0521c7538255bbbcd4982d21dda3,
which is visible if you look at _MTN/revision:

-------------------- 8< --------------------
: ; cat _MTN/revision 
format_version "1"

new_manifest [933940c810aca3b0edd8651fb5b5848141cac511]

old_revision [ce577c763adf0521c7538255bbbcd4982d21dda3]
-------------------- 8< --------------------

However, here's the weird thing:

-------------------- 8< --------------------
: ; mtn automate get_current_revision_id
d2699bef76a3a8d1aa0b655104d0738d7dbf2b68
-------------------- 8< --------------------

A little bit of experiment shows what it does:

-------------------- 8< --------------------
: ; cat _MTN/revision | openssl sha1
d2699bef76a3a8d1aa0b655104d0738d7dbf2b68
-------------------- 8< --------------------

So, what this means is that 'mtn automate get_current_revision_id'
will *never* show and existing committed revision, even when the
workspace contains no changes at all.

I do not think this is acceptable.  It currently beats me how this
should be properly fixed, though.

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis