Hi,
Zack Weinberg wrote:
Implemented now and pushed as
81798740507c3414f4833a7451f9b559ca03a167, with tests even.
Wow, cool, thanks!
Markus
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
Ok. So if we add rename, add and drop status to the automate inventory
output, we don't need to output the node ids.
If we leave out the node ids we certainly need also another way to match
rename pairs. Until that hasn't been implemented they have to been cept in.
Thomas.
--
ICQ: 85945241
Thomas Moschny, 2007-04-12:
On Tuesday 03 April 2007, Christian Ohler wrote:
Pressing C-x V = will bring up the tree diff buffer. (What monotone
calls a workspace is called a tree in DVC.) This buffer shows the
list of all modified files in the tree as well as the diffs for those
files.
Thomas Keller, 2007-04-26:
Stephen Leake schrieb:
I'm not clear what the rationale is for the node ids; what subsequent
commands would use them?
F.e. automate get_file (obviously there is a version available now which
takes the file path and revision_id).
Just to be clear, automate
Zack Weinberg [EMAIL PROTECTED] writes:
On 4/28/07, Stephen Leake [EMAIL PROTECTED] wrote:
Here is a possible fix for umask in key_store.cc on MinGW:
I don't mean to rain on your parade,
No problem; I was just trying to get things to compile, and getting
back into writing C++.
but I really
Thomas Keller wrote:
Derek Scherger schrieb:
I don't think this is correct. Listing either old or new name of a
renamed path will include the *node* in a restriction and including the
node will list both old and new names in the resulting inventory output.
I've actually tested this out
Thomas Keller wrote:
Yep, I'm interested in the content hashes. But apparently some people
think this would generate too much overhead. I have no strong personal
feelings for/against that feature, so its entirely optional.
They have already been computed and are available so adding them
