Situation:
- 2 branches with slightly different explorations of the same
codebase (where 1 may not yet exist )
- 1 'main branch' which is ahead of those 2.
Goal: partial propagation of main into both
$ mtn explicit_merge `mtn automate select t:checkpoint` `mtn automate
heads`
On Mon, Jun 05, 2006 at 11:49:36AM +0200, Marcel van der Boom wrote:
I assume it tries to create the same a3a93... rev.
Couldn't monotone recognize oh, it's already there, lets put the
cert on it then or am I doing something wrong?
It could, and there may still be an issue here, but you
On Sun, 2006-06-04 at 17:14 +0200, Benoît Dejean wrote:
Hey, i'm running a 0.26 server like this :
$MTN --db=$DB serve 'fr.placenet*'
with read-permissions :
comment Placenet Fr
pattern fr.placenet*
allow [EMAIL PROTECTED]
allow [EMAIL PROTECTED]
allow [EMAIL PROTECTED]
and
On 5 jun 2006, at 13:48, Daniel Carosone wrote:
On Mon, Jun 05, 2006 at 11:49:36AM +0200, Marcel van der Boom wrote:
I assume it tries to create the same a3a93... rev.
Couldn't monotone recognize oh, it's already there, lets put the
cert on it then or am I doing something wrong?
It could,
Haven't seen anything in the archives about this specific issue. For a
while, now on 0.26, we have some case sensitivity issues which causes
monotone to report redundant changes. We are entirely using monotone
on Windows.
Here's sample output from mtn diff:
# patch src/Data/Common/Person.cs
#
Le lundi 05 juin 2006 à 06:49 -0500, Timothy Brownawell a écrit :
On Sun, 2006-06-04 at 17:14 +0200, Benoît Dejean wrote:
They won't be able to sync that branch again, since sync is r/w and
they're not allowed to read that branch. They also won't be able to push
it again, but this is more
Is monotone-viz 0.14 meant to be able to pull the options and revision
from _MTN as it does for MT? It doesn't seem to work for me.
Cheers,
Shaun
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
On 6/5/06, Shawn Samuel [EMAIL PROTECTED] wrote:
Haven't seen anything in the archives about this specific issue. For a
while, now on 0.26, we have some case sensitivity issues which causes
monotone to report redundant changes. We are entirely using monotone
on Windows.
Here's sample output
On Mon, 2006-06-05 at 21:06 +0200, Benoît Dejean wrote:
Le lundi 05 juin 2006 à 06:49 -0500, Timothy Brownawell a écrit :
On Sun, 2006-06-04 at 17:14 +0200, Benoît Dejean wrote:
They won't be able to sync that branch again, since sync is r/w and
they're not allowed to read that branch.
Nathaniel Smith wrote:
On Sun, Jun 04, 2006 at 10:17:50PM -0500, Timothy Brownawell wrote:
Why do we need to hide boost::format? Should we just use extern
template for our % and make having an instantiation of that be another
requirement for types we want to format, along with having an
Shaun Jackman [Monday 5 June 2006] :
Is monotone-viz 0.14 meant to be able to pull the options and
revision from _MTN as it does for MT? It doesn't seem to work for
me.
No but the latest revision on the venge.net repository, yes.
I should have released that ages ago, sorry.
--
On 6/5/06, Olivier Andrieu [EMAIL PROTECTED] wrote:
No but the latest revision on the venge.net repository, yes.
I should have released that ages ago, sorry.
Off-topic, but I won't release the next monotone-viz for Debian for a
couple weeks anyways. I'm going on vacation to Montréal for a
On Mon, Jun 05, 2006 at 02:19:00PM +0200, Marcel van der Boom wrote:
True, and doing this manually gives (me) a sufficient hint to do it
manually, after the error. It becomes more hairy when this runs from
a script.
Leaving aside the error handling, there's no need to do the merge
twice
On Tue, Jun 06, 2006 at 08:02:26AM +1000, Daniel Carosone wrote:
Clearly there is a user interface issue here in the way the error is
detected and reported which could be more helpful or less panicky, and
monotone could perhaps be smarter in how it responds to some
situations.
I presume
14 matches
Mail list logo
