On Thu, 2006-02-02 at 07:42 +0100, Richard Levitte - VMS Whacker wrote:
I must say that I feel nervous handing the decision to a lua hook.
There's the strong possibility that a user somewhere will get
creative and that chaos will follow. If there's an attribute saying
that a file shouldn't be
Richard Levitte - VMS Whacker spake unto us the following wisdom:
In message [EMAIL PROTECTED] on Wed, 1 Feb 2006 21:19:37 -0500, Ethan
Blanton [EMAIL PROTECTED] said:
eblanton Given this set of rules, I claim that *text conversions* are
eblanton as optimal as can be expected. Monotone seems
In message [EMAIL PROTECTED] on Thu, 02 Feb 2006 08:55:47 +0100 (CET),
Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
richard In message [EMAIL PROTECTED] on Thu, 02 Feb 2006 07:58:24 +0100,
rghetta [EMAIL PROTECTED] said:
richard
richard birrachiara I think monotone should *not* change
Steven E. Harris [EMAIL PROTECTED] writes:
More generally, can anyone offer a means to use XEmacs on Cygwin as
the merge editor? I may be able to solve the latter if I can get
more assistance with the former.
Here's what I came up with after much frustration.
First, I created the following
On 2/2/06, rghetta [EMAIL PROTECTED] wrote:
I think monotone should *not* change the file unless instructed to do
so, i.e. every file should be non-transformable by default.
Transformable files instead could be converted between equivalent
forms, e.g. with a different line endings, with a
Michael Milner wrote:
Hi,
I've been following along on recent developments and am very pleased with
the stability of 0.26rc1.
Is there currently any kind of roadmap to the first stable release?
I've been using monotone extensively for some small projects with great
success, but I am a bit
On Thu, Feb 02, 2006 at 07:11:01AM +0100, Richard Levitte - VMS Whacker wrote:
Oh, so you and I do understand reversible differently. To me,
reversible means there is a 1 to 1 mapping between the original file
(the one being checked in) and the resulting file (the one being check
out) in
On Thu, 2006-02-02 at 11:45 -0800, Graydon Hoare wrote:
Is this a clear enough position for everyone?
Dear Graydon,
My original question was very simple: how you specify what treat by a
sequence of lines means? Does it mean converting all weird combinations
of CR and LF into line-ending or
I'm only commited source to branch net.venge.monotone, and have no other
branches in my local database (never get all branches).
http://viewmtn.angrygoats.net/branch.psp?branch=net.venge.monotone.annotate
Why are my change also list in branch net.venge.monotone.annotate with
viewmnt?
This
On Wednesday 01 February 2006 21:41, Ethan Blanton wrote:
With this condition, a correct definition of the end-of-line sequence
for the current platform,
I don't think Monotone should count on files obeying the platform's
end-of-line sequence. I mostly work in Windows, but even so I have to
On Thursday 02 February 2006 18:48, Graydon Hoare wrote:
1. workspace file - std::vectorstd::string
2. workspace file - std::vectorstd::string
...
Operations 1 and 2 are done by splitting or joining. The split and join
operations are governed by the following rules:
- At first,
On Thu, 2006-02-02 at 21:48 -0600, Glen Ditchfield wrote:
For operation 2, this is good. For operation 1, would it be good to split in
a platform-agnostic manner, provided that the file is internally consistent?
- If the file contains LFs but no CRs, split on LFs.
- If the file contains CRs
12 matches
Mail list logo
