On Wed, Jul 12, 2006 at 08:53:57PM +0100, Ganesh Sittampalam wrote:
Some random comments about the bits I can digest easily:
On Wed, 12 Jul 2006, David Roundy wrote:
2. We're going to have to be doing considerably more rearranging and
modifying of patches than in current darcs, in which a
On Thu, 13 Jul 2006, David Roundy wrote:
On Wed, Jul 12, 2006 at 08:53:57PM +0100, Ganesh Sittampalam wrote:
On Wed, 12 Jul 2006, David Roundy wrote:
This would give us for free the feature that patches that are
identical except in name do not conflict.
I've said this before, but please
On Thu, 13 Jul 2006, David Roundy wrote:
[identical patches conflicting or not]
But it's not a conflict, that's the point.
If it is a conflict, then we can easily resolve it and push the resolution
to everyone else.
If it isn't a conflict, then we're in trouble if we wanted it to be one,
* Improved SSH ControlMaster check.
Remove spurious error messages seen in issue200 and issue219.
Fixes issue218.
Eric, this looks fragile to me. Is there any way to avoid it?
Juliusz
___
* Do not redirect to /dev/null when calling ssh.
Eric, I cannot apply this until we decide about the previous patch.
Juliusz
___
darcs-devel mailing list
darcs-devel@darcs.net
/foo/bar/myDarcsRepo/_darcs/inventories/20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz:
openBinaryFile: does not exist (No such file or directory)
Aye, same thing here. I don't get the issue with a version from 15 May,
I do get it with the current unstable.
I'll try to work
You're guilty, Eric.
I've got the file
20030921115726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz
but with your recent changes, it's trying to open
20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz
Obviously, your cleanDate changes are the culprit. I'm reverting them
I've got the file
20030921115726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz
^
but with your recent changes, it's trying to open
20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz
^
Obviously, your cleanDate changes are the culprit.
Sorry
New submission from Stefan Karrmann [EMAIL PROTECTED]:
Dear all,
I got an error `fromJust error at Push.lhs:134 compiled 14:34:38 Apr 15 2006'
in darcs:
$ pushd ~/eigen/publiziert/www-arcor/haskell/pfp
$ darcs initialize
$ ls -lR
.:
insgesamt 0
drwxr-xr-x 6 sk sk 184 2006-07-11 20:37 _darcs
On Thu, 13 Jul 2006, David Roundy wrote:
The one person who has darcs warn him about changes which are members
of more than one patch will notice and push a fix (in the relatively
rare case that it is necesary) to everyone else, just like any other
bug in the code.
Ah, yes, ok.
The only
[btw: I suggest we stop CCing so much stuff to darcs-devel. I'm sure
everyone there is aware there's active semantic discussion going on, and
can follow it on darcs-conflicts if they want. There seems little point in
having darcs-conflicts as a separate list if everything goes to
darcs-devel
Hi Juliusz and list,
(Note: away from home till the 24th, so probably no in-depth thoughts
from me till then)
On 7/13/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
* Improved SSH ControlMaster check.
Eric, this looks fragile to me. Is there any way to avoid it?
I think so. Let's
Here's the description of what the proposed new option does:
+To scrutinize each patch before recording it in the local repository,
+supply a command with \verb!--check-patch!.
It sounds rather similar to what --test does, although I can see the
intent is different.
The docs referenced
13 matches
Mail list logo
