On Tue, Oct 25, 2005 at 06:13:53PM -0400, Peter Portante wrote:
> So can I just use another name for the directory besides BUG? Or do I have
Yes.
> to undo what I have done first? And if so, how do I undo it?
I'm assuming you still have a working copy whose MT/work contains the
text:
rename_fil
So can I just use another name for the directory besides BUG? Or do I have
to undo what I have done first? And if so, how do I undo it?
-peter
On 10/25/05 4:56 PM, "Nathaniel Smith" <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 25, 2005 at 10:15:12AM -0400, Peter Portante wrote:
>> Nathaniel,
>>
>>
On Tue, Oct 25, 2005 at 10:15:12AM -0400, Peter Portante wrote:
> Nathaniel,
>
> This is what I have. Sorry if this is not helpful. I can try to reproduce
> this again if it isn't.
Ah-hah, I see what the problem is. You had a file named BUG; then in
one commit you renamed it to BUG.file; then in
On Sun, Oct 23, 2005 at 09:03:00PM -0400, Peter Portante wrote:
> monotone rename BUG.file BUG/BUG.orig
> monotone: adding topc-2.5.1-Beta7-pajp/src/mpinu/BUG.file ->
> topc-2.5.1-Beta7-pajp/src/mpinu/BUG/BUG.orig to working copy rename set
> monotone: fatal: std::logic_error: ../change_set.cc:380:
[Frodo:topc-2.5.1-Beta7-pajp/src/mpinu] portante% monotone commit -m "Add
BUG directory and move original BUG file into that directory"
monotone: beginning commit on branch 'edu.neu.ccs.csg280.topc.debug'
monotone: fatal: std::logic_error: ../change_set.cc:380: invariant
'I(isect.empty())' violated
monotone rename BUG.file BUG/BUG.orig
monotone: adding topc-2.5.1-Beta7-pajp/src/mpinu/BUG.file ->
topc-2.5.1-Beta7-pajp/src/mpinu/BUG/BUG.orig to working copy rename set
monotone: fatal: std::logic_error: ../change_set.cc:380: invariant
'I(isect.empty())' violated
monotone:
monotone:
monotone: t