On Wed, Dec 14, 2005 at 11:24:14PM +0100, Juliusz Chroboczek wrote:
Hmm... I'd rather this didn't use a hidden file, but instead deleted
it if everything goes well.
Juliusz,
I agree. I was mimicking the .darcs-temp-mail behavior which is
probably a bad idea.
The attached patch fixes this.
On 12/15/05, Will [EMAIL PROTECTED] wrote:
Wed Dec 14 21:54:53 MST 2005 Will [EMAIL PROTECTED]
* really suppress output in win32 exec
Hehe :-) That's a nice idea. This time it works for me, too.
Thanks,
--Esa
___
darcs-devel mailing list
On Thu, Dec 15, 2005 at 01:38:10AM +0100, Juliusz Chroboczek wrote:
but perhaps it will only result in a harmless unable to apply
patch.
I would expect to get the ``perhaps this is a partial repository''
error.
I tried to fake it by backing up the inventory before amending,
then restoring
Hi Juliusz et al,
This is a resend of an amended multirepo pull patch, since there was a
conflict with the send --subject patch.
David
Mon Sep 19 08:50:12 EDT 2005 David Roundy [EMAIL PROTECTED]
* add support for pulling from multiple repositories simultaneously.
Thu Dec 15 07:28:08 EST
New submission from David Roundy [EMAIL PROTECTED]:
It would be nice to have roundup-darcs integration, so that bugs could be
automatically marked as resolved in various branches based on whether
a certain patch is present in a certain version.
I'm imagining that we'd add two fields to each
On 12/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Crud, being able to read from stdin is a really ugly side effect of
using system() but I can't see a way around it.
I don't know if this is a reasonable kludge, but how about darcs looks for the
GPG password prompt, then reads from
On Thu, Dec 15, 2005 at 12:32:47PM +0100, Tommy Pettersson wrote:
I have not checked that this faked race condition can happen
in reality, but since Pull doesn't lock the repo, anything
could happen if the repo is altered concurrently.
2 possible solutions that spring to mind are:
* Put the
It was already filtering out special characters.
Ah, sorry.
+validFileChar char = isAlpha char || isDigit char || char == '_'
So here you filter out everything including dashes...
+ where name = map (\c - if validFileChar c then toLower c else '-') summary
...which you then replace with
Sorry, it needs more work. I know it's annoying, but that's important
missing functionality you're implementing, and I'd like it to be just
right.
+ where f = .darcs-record
There's no reason why that should be a hidden file (one that starts
with a dot); quite the
I was wondering, would it be an idea to have submitted patches
be forwarded to the bug tracker instead of darcs-devel?
They would still be visible on darcs-devel, but it might be
easier to track them that way.
I actually prefer it this way. Patches are being tracked by Darcs:
Just do ``darcs
* clarify wording of w in patch selection.
- w: wait and decide later, defaulting to no\n\n++
+ w: wait and let darcs decide later, defaulting to no\n\n++
I'm rejecting this one -- I actually think it confuses matters more
than it clarifies them.
But perhaps *something* should be
I have not checked that this faked race condition can happen
in reality, but since Pull doesn't lock the repo, anything
could happen if the repo is altered concurrently.
I'm surprised. I was convinced that amend is the equivalent of
unrecord followed with record.
2 possible solutions that
On Thu, Dec 15, 2005 at 05:31:12PM +0100, Juliusz Chroboczek wrote:
I have not checked that this faked race condition can happen
in reality, but since Pull doesn't lock the repo, anything
could happen if the repo is altered concurrently.
I'm surprised. I was convinced that amend is the
On Thu, Dec 15, 2005 at 05:04:31PM +0100, Juliusz Chroboczek wrote:
Sorry, it needs more work. I know it's annoying, but that's important
missing functionality you're implementing, and I'd like it to be just
right.
+ where f = .darcs-record
There's no reason
Some background. Darcs originally used _darcs/current for the pristine
directory. Starting with 1.0.2rc1, all versions of Darcs have been able to
understand either name, but still create pristine directories under
_darcs/current. The first released version with support for _darcs/pristine
was
New submission from Samuel Bronson [EMAIL PROTECTED]:
It would be nice to be able to look through the patches in ones own repo in the
same way that one can look through patches in darcs pull. unpull sorta helps
with that, but it doesn't feel warm and fuzzy, and it doesn't help much with
Juliusz,
On 12/15/05, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
Some background. Darcs originally used _darcs/current for the pristine
directory. Starting with 1.0.2rc1, all versions of Darcs have been able to
understand either name, but still create pristine directories under
17 matches
Mail list logo
