[Monotone-devel] Re: .mt-ignore and .cvsignore files

Nathaniel Smith <[EMAIL PROTECTED]> writes: > On Sat, May 14, 2005 at 12:04:57AM -0700, David Brown wrote: >> On Fri, 13 May 2005 20:39:31 -0700, Nuno Lucas <[EMAIL PROTECTED]> >> wrote: >> >> >I understand your point. On the other hand there is no way to be fully >> >sure they will always be t

Re: [Monotone-devel] monotone automate stdio

On 5/17/05, Joel Crisp <[EMAIL PROTECTED]> wrote: > Yep, a number at the beginning of each line. It lets you detect the start of > the next header, distinguish different types of output > easily, handle optional or repeated blocks of output etc. It also allows you > to detect badly or prematurely

[Monotone-devel] Re: monotone automate stdio

Joel Crisp <[EMAIL PROTECTED]> writes: > Hi > > Just a small comment; maybe a format using the numeric prefix familiar to us > all from RFCs like > > 200 OK UNKNOWN test/foo > 201 foo.h > 201 foo.c > > etc. > > This format is more likely to be parsable with existing libraries and is > familiar t

[Monotone-devel] [patch]--depth for monotone ls

I took a look at adding support for limiting monotone's recursive predilections, which seems to be important option for some. I need it for better zsh file completion. Anyway I was able to add it in suprisingly few (to me at least) # of lines. I used --depth=X as the option and tested the code by

Re: [Monotone-devel] monotone update overwrites local changes

On Sat, May 14, 2005 at 10:21:32PM -0600, Derek Scherger wrote: > Nathaniel Smith wrote: > > On Wed, May 11, 2005 at 08:47:56PM -0600, Derek Scherger wrote: > >>How about just skip the file and keep going, perhaps with a warning like > >>"preserving existing file ...". > > > > This violates "refus

[Monotone-devel] Test message

Sorry about this, but i got nothing back from my subscribe attempt. -- Peter B. West Folio ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongn

[Monotone-devel] Projects using monotone?

I have been thinking of finally moving some of my CVS-managed projects to monotone. For one of them, I was asked what other projects are using monotone, as some kind of "proof of maturity" (I know, it's not regarded as mature enough for production according to some. I don't entirely agree). So,

Re: [Monotone-devel] monotone update overwrites local changes

On Sat, 2005-05-14 at 21:21, Derek Scherger wrote: > it seems to me that there are three settings for such a hook > > - fail on pre-existing files > (cvs, svn, etc. do this) > > - preserve pre-existing files but continue > (which I think would be useful occasionally) > > - clobber pre-existi

[Monotone-devel] [Fwd: never two without three: the %+ specifier]

-Forwarded Message- From: rghetta <[EMAIL PROTECTED]> To: Emile Snyder <[EMAIL PROTECTED]> Subject: never two without three: the %+ specifier Date: 16 May 2005 17:12:41 +0200 Ahem. Here comes another patch (I hope you don't get upset by this endless stream) :) This patch add a %+ specifi

[Monotone-devel] Bitkeeper -> Monotone?

I have an XSL-FO implementation project, Folio, hosted on bkbits.net. I need to find another SCM, and another host. Approximate current size of the project is 2500 files totalling 25Mb, which includes jar files of required ant, xalan and xerces binaries. Final size should not exceed 3500 file

Re: [Monotone-devel] Re: 3-way merge considered harmful

On Friday 13 May 2005 07:18, Nathaniel Smith wrote: > Another option is to use something like codeville-merge, in which a > version is defined by its state, but its state includes information > on "how it got that way". Right. That's a variant along the way to a full Darcs-like system. > ... A co

Re: [Monotone-devel] monotone automate stdio

Timothy Brownawell wrote: There've been some requests for a way to run multiple automate commands without needing a new monotone process for each. There's now a new command, "monotone automate stdio" that takes automate commands on stdin. Currently, it prefixes the output of each command with the l

Re: [Monotone-devel] monotone automate stdio

Hi Just a small comment; maybe a format using the numeric prefix familiar to us all from RFCs like 200 OK UNKNOWN test/foo 201 foo.h 201 foo.c etc. This format is more likely to be parsable with existing libraries and is familiar to people who have worked with other software. Joel Timothy Brownaw