On Thu, Jun 30, 2005 at 06:24:58PM -0400, Eric Kidd wrote:
Since monotone doesn't handle directory moves as gracefully as it
could, this strategy only works if the 'bar' directory appears in the
same place in both the vendor branch and the head branch.
Not sure what you mean; monotone does
On Sat, Jun 25, 2005 at 01:01:44PM -0500, Brian Downing wrote:
On Fri, Jun 24, 2005 at 01:15:10PM -0700, Nathaniel Smith wrote:
If someone were to fix the b: selector (as described at
http://venge.net/monotone/quickies.html, last item), then this would
just be
$ for R in `monotone
On 7/1/05, Nathaniel Smith [EMAIL PROTECTED] wrote:
Not sure what you mean; monotone does handle directory moves
gracefully, as far as I know.
My understanding is that if I add directory D1 on branch A, propagate
to branch B, and move D1 to D2, that everything will work fine.
But without an
Hello,
Don't know if this is really a bug but monotone thinks so.
I was pulling the monotone sources like this to host 'vargen':
monotone --key= pull off.net net.venge.monotone
At the same time I synced some work done on host 'bamse' to the same db
as pulling monotone sources to on host
On Fri, 2005-07-01 at 19:44 +0200, Johan Bolmsjo wrote:
Hello,
Don't know if this is really a bug but monotone thinks so.
No, just a bad error message.
I was pulling the monotone sources like this to host 'vargen':
monotone --key= pull off.net net.venge.monotone
At the same time I
On Fri, Jul 01, 2005 at 07:59:11AM -0400, Eric Kidd wrote:
On 7/1/05, Nathaniel Smith [EMAIL PROTECTED] wrote:
Not sure what you mean; monotone does handle directory moves
gracefully, as far as I know.
My understanding is that if I add directory D1 on branch A, propagate
to branch B, and