[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: Trying to understand the ideas behind cherrypic
Richard Levitte - VMS Whacker
Re: [Monotone-devel] Re: Trying to understand the ideas behind cherrypicking...
Thu, 25 Nov 2004 21:13:31 +0100 (CET)
In message <address@hidden> on Thu, 25 Nov 2004 19:42:09 +0000, Bruce Stephens
monotone> Richard Levitte - VMS Whacker <address@hidden> writes:
monotone> > Command name ideas:
monotone> > cherrypicking: monotone transplant ID [BRANCH]
monotone> > disallow certain revisions: monotone disallow transplant ID
monotone> I don't much like "transplant", but I'm not quite sure why.
I love it, and I'm not quite sure why :-).
monotone> Why not just use an optional argument (or arguments) to
Because it seems to me that this would break the current command
structure of monotone. Besides, propagate is meant to work as a
one-way merge, which is quite different and really creates a very
different situation for later merges.
monotone> OK, propagate (like merge) doesn't currently work on a
monotone> working tree, so that doesn't quite work, but I think that's
monotone> probably wrong (and Graydon seemed to agree).
With that sentence, I didn't quite catch what part was wrong, but
then, english isn't my native language, so I may be missing a nuance
Anyway, I actually meant that "monotone transplant" (or whatever we
wanna call it, I don't really care that much) would work against the
database directly the same way propagate does. The only reason do
make the BRANCH argument optional is that it could use the info from
MT/options if you stand in a working directory.
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
Richard Levitte address@hidden
"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