Re: [Monotone-devel] Re: line endings with 0.31

2006-11-22 Thread Brian May
> "J" == J Decker writes: J> On a note from some windows programmer that appreciated the J> conversions when checking out linux-like sources to have J> 'notepad' work as a browser; While some days I can agree, in J> the end, one must make sacrifices and call a goat a goat, and

Re: [Monotone-devel] Re: line endings with 0.31

2006-11-22 Thread J Decker
I have to state a vote. I had lengthy discussions with CVS on similar topics, and resorted to hacking my own CVS to work properly, that is, if a text file has \r\n, keep \r\n, do not convert to \r\r\n. If a text file has \r or \n in some sequence [\r\n]* this is an end of line, if \n's exist mult

Re: [Monotone-devel] Re: line endings with 0.31

2006-11-22 Thread J Decker
The logic for determining line endings within reasonable limits is entirely feasible in practice as well as theory. On 11/21/06, Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> wrote: I've been thinking about this issue a number of times, and have discussed it as well. A thought that came to

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Nuno Lucas
On 11/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Does that mean that you have C code in ASCII with comments embedded in a completely different characte set? What I called IBM-860 is just a variation of ASCII. It's the same as having an UTF-8 C source file with comments in a foreigner l

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Nuno Lucas
On 11/22/06, Thomas Moschny <[EMAIL PROTECTED]> wrote: On Wednesday 22 November 2006 22:33, Nuno Lucas wrote: > Don't mix character encoding problems with the end-of-line issue. They > are very different beasts. But in order to know what you are doing when converting different types of eol into

[Monotone-devel] an ordinary, everyday success

2006-11-22 Thread hendrik
Developers never hear from happy users. so... A minor success story. Up to now, monotone was a peculiar way for Dad to store his code. Now my son has a laptop as well as a desktop, and he suddenly sees the light. A repository on his laptop, another on his desktop, regular sync, and he's curre

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread hendrik
On Wed, Nov 22, 2006 at 08:05:31PM +0100, Richard Levitte - VMS Whacker wrote: > > hendrik> Can we uncompress compressed files so as top better > hendrik> diff/merge the contents and recompress on checkout? This > hendrik> might be very helpful for openoffice files. > > Uhmm, I seriously thi

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Wed, 22 Nov 2006 21:33:33 +, "Nuno Lucas" <[EMAIL PROTECTED]> said: ntlucas> In my opinion, should be up to the user to know how to handle ntlucas> the text encoding, not monotone. As long as all users in the same project agree... Cheers, Richard - Ple

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread hendrik
On Wed, Nov 22, 2006 at 09:33:33PM +, Nuno Lucas wrote: > On 11/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >If we use an internal line ending standard, we should consider the > >possibility of using the standard newline character NEL, "Next Line", > >0x85, unicode U+0085. > > You ar

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Thomas Moschny
On Wednesday 22 November 2006 22:33, Nuno Lucas wrote: > Don't mix character encoding problems with the end-of-line issue. They > are very different beasts. But in order to know what you are doing when converting different types of eol into each other, you have to know what the encoding of the fi

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Nuno Lucas
On 11/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: If we use an internal line ending standard, we should consider the possibility of using the standard newline character NEL, "Next Line", 0x85, unicode U+0085. You are forgetting I can (and actually I am) versioning C files with text comm

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Wed, 22 Nov 2006 10:05:06 -0500, [EMAIL PROTECTED] said: hendrik> > - We need to treat files as binary unless told otherwise. hendrik> >This I regard as a fact. (see the problem with screwed hendrik> >up files without the user knowing about it) hendrik>

Re: Bug#384565: [Monotone-devel] Re: Bug#384565: monotone - FTBFS: Build killed with signal 15

2006-11-22 Thread Nathaniel Smith
On Wed, Nov 22, 2006 at 09:54:42AM -0700, Shaun Jackman wrote: > On 11/22/06, Roman Zippel <[EMAIL PROTECTED]> wrote: > ... > >> 1. Is this more likely a bug in Boost or a bug in monotone? > >> 2. Is it reasonable to workaround this bug by removing > >> -DBOOST_SP_DISABLE_THREADS? > >> 3. Is it wor

Re: Bug#384565: [Monotone-devel] Re: Bug#384565: monotone - FTBFS: Build killed with signal 15

2006-11-22 Thread Roman Zippel
Hi, On Tue, 21 Nov 2006, Shaun Jackman wrote: > It appears the BOOST_SP_DISABLE_THREADS is the source of monotone's > cross-platform issues on Debian. Namely, that monotone fails to run > (deadlock) on s390, hppa, sparc, mips, and mipsel, but runs fine on > i386, amd64, ia64, alpha and powerpc [1

Re: Bug#384565: [Monotone-devel] Re: Bug#384565: monotone - FTBFS: Build killed with signal 15

2006-11-22 Thread Shaun Jackman
On 11/22/06, Roman Zippel <[EMAIL PROTECTED]> wrote: ... > 1. Is this more likely a bug in Boost or a bug in monotone? > 2. Is it reasonable to workaround this bug by removing > -DBOOST_SP_DISABLE_THREADS? > 3. Is it worth going to the extra effort to only define > -DBOOST_SP_DISABLE_THREADS on t

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread hendrik
On Wed, Nov 22, 2006 at 10:40:58AM +0100, Richard Levitte - VMS Whacker wrote: > In message <[EMAIL PROTECTED]> on Tue, 21 Nov 2006 23:59:41 -0800, "Justin > Patrin" <[EMAIL PROTECTED]> said: > > papercrane> I haven't read the line endings with 0.31 thread yet > papercrane> but...ugh. Is it reall

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Wed, 22 Nov 2006 01:31:41 -0800, Nathaniel Smith <[EMAIL PROTECTED]> said: njs> Door C: .mtn-autoprops? Sounds like a good idea to me! (well, until there's something better, of course) Cheers, Richard - Please consider sponsoring my work on free software.

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Tue, 21 Nov 2006 23:59:41 -0800, "Justin Patrin" <[EMAIL PROTECTED]> said: papercrane> I haven't read the line endings with 0.31 thread yet papercrane> but...ugh. Is it really necessary to mangle line endings papercrane> when checking out files? I mean really

Re: [Monotone-devel] line endings as project policy

2006-11-22 Thread Nathaniel Smith
On Tue, Nov 21, 2006 at 11:14:45PM -0700, Derek Scherger wrote: > So, would this be better as a (shared and versioned) project policy > entry with line ending styles specified by file name patterns. It seems > like it would handle the case of added files, that match some policy > pattern, better

[Monotone-devel] Re: line endings as project policy

2006-11-22 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin Patrin schreef: > On 11/21/06, Derek Scherger <[EMAIL PROTECTED]> wrote: >> So, would this be better as a (shared and versioned) project policy >> entry with line ending styles specified by file name patterns. It seems >> like it would handle t

Re: [Monotone-devel] Re: line endings with 0.31

2006-11-22 Thread Thomas Moschny
On Tuesday 21 November 2006 23:51, Brian May wrote: > Recently we got a sourceforge project converted from CVS to > subversion. > > The process automatically checked in the files using text mode > conversions. > > The result was that a tar.gz file (yes, having this in the project is > somewhat weir