monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: mtn split (Was: [Monotone-devel] Best practice using monotone)


From: Larry Hastings
Subject: Re: RFC: mtn split (Was: [Monotone-devel] Best practice using monotone)
Date: Thu, 24 Aug 2006 15:40:51 -0700
User-agent: Thunderbird 1.5.0.5 (Windows/20060719)

Chad Walstrom wrote:
I don't think this would be possible.  By the time you are inside the
editor to record your comment, monotone has already selected the files
to commit in the new revision.  The best you could do is abort the
commit by comparing the log template before and after.  If there were
any "MTN:" prefixes missing, abort.  If there was no comment, abort.
Surely it's possible.  How about:
  1. Compare the MTN: prefixes in the comment against what mtn originally generated.
  2. If they don't match:
    1. Generate an "ignore list" of the files that were removed from the MTN: prefix lines.
    2. Throw away the current calculated whatever ("changeset"? "revision"?).
    3. Generate a new whatever, but this time ignore all files on the "ignore list".
  3. Submit the whatever.
And don't call me Shirley,


larry

reply via email to

[Prev in Thread] Current Thread [Next in Thread]