[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] "prune-branch" cert implementation issues.
From: |
Richard Levitte - VMS Whacker |
Subject: |
Re: [Monotone-devel] "prune-branch" cert implementation issues. |
Date: |
Mon, 06 Jun 2005 02:14:01 +0200 (CEST) |
In message <address@hidden> on Sun, 05 Jun 2005 17:53:07 -0400, Michael Stone
<address@hidden> said:
mstone> I'm attempting to give people a clean way to mark a revision
mstone> as "no-longer-a-head-for-branch-X". There are two use cases
mstone> for a feature like this one:
mstone>
mstone> 1) To ignore old branches which have subsequently been merged
mstone> into the mainline.
I'm not sure I understand how that would work. Basically, you'd make
certain branches head-less, but how does that stop anyone from
updating explicitely to a specific revision (maybe even the marked
revision) and continuing to work from there. Also, since this is a
distributed environment, what is supposed to happen when you get
revisions synced in that are children of the revision you marked as
no-longer-head?
To me, this seems like a moot point, or maybe a red herring. I
haven't quite decided. It feels like trying to make a distributed SCM
bend over backwards to behave like a centralised SCM...
mstone> 2) To mark revisions as unsuitable for merging.
Again, what if someone else has already done so in his/her database.
What's to happen with the children? Are they supposed to end up in
void?
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