Hi Everyone
[I am not a regular reader of this list, so please bear with me if this
horse has already been beaten to death.]
In darcs, I can record changes to a file that has been renamed by someone
else and the two changes happily merge with the expected result. Formally
speaking, the two
Petr Rockai wrote:
Ben Franksen [EMAIL PROTECTED] writes:
*darcs should allow to record changes to the content of a file that has
been removed (or wasn't even added in the first place)*
[snip]
What do you think?
Well, I think this is a good idea.
Good!
I think I may have already
Ketil Malde wrote:
Ben Franksen [EMAIL PROTECTED] writes:
*darcs should allow to record changes to the content of a file that has
been removed (or wasn't even added in the first place)*
[...]
What do you think?
I'm no darcs expert, so perhaps that is why I am confused.
I am neither so
Doug Philips wrote:
On Tuesday, November 27, 2007, at 01:24PM, Ketil Malde wrote:
Ben Franksen writes:
.. This would let you have different files
with the same name at different times.
The problem I have with ghosts of deleted files is precisely that once a
file is deleted, a new file can
Ketil Malde wrote:
Thanks, I'm less confused now.
Good, me too ;-) I am working this out as I go...
So this would make it possible to
a) pull patches that touch deleted files, e.g. for that crucial bug
fix from the stable tree that also touches some files that have been
obsoleted - and
Nathan Gray wrote:
I would like to be able to do something like:
darcs changes --matches content 'PARTIAL CONTENT OF LINE'
or perhaps instead of 'content' the keywords could be 'add' and
'remove'.
That would be an extremely cool feature, IMHO.
Cheers
Ben
Eric Kow wrote:
Could you create a minimal test case that demonstrates this? I don't
see anything on the bugtracker, so that may be useful as well.
Actually, I've just sent a patch with a small demonstration. Is this
the same issue you're facing? If not, could you add to that test.
David Roundy wrote:
Fri Jun 6 16:15:34 BST 2008 Eric Kow [EMAIL PROTECTED]
* Demonstrate 'hidden conflicts' bug (old format).
Applied, thanks!
I wanted to send a patch to add the missing --ignore-times options to this
test but it is impossible to record anything. Each time I try to
Eric Kow wrote:
* fix issue #918: use simplePrinters for xml output in darcs
changes command
Thanks indeed!
Note that in the future, it would be best to start instead with
resolve issue918 (note the spaces, etc) so that it will be picked up
by our bugtracker integration. Yay,
David Roundy wrote:
On Fri, Jun 13, 2008 at 06:18:07PM +, [EMAIL PROTECTED] wrote:
Fri Jun 13 18:11:47 BST 2008 Eric Kow [EMAIL PROTECTED]
* Canonize Benjamin Fraksen.
Applied, thanks!
Ahrgh, no! Please, it's Franksen, not Fraksen.
:-)
Thanks
Ben
Luke Palmer wrote:
On Fri, Aug 1, 2008 at 3:45 PM, Eric Kow [EMAIL PROTECTED] wrote:
I would contribute to darcs if only...
I haven't used darcs much, so it's possible that I'll be forced to start
contributing by my own binding hypothetical.
I would contribute to darcs if only it had
Ketil Malde wrote:
The consequences of moving to the darcs-2 format are a bit unclear to
me. For instance, I'd like to keep my main (export) repo in darcs-1
format, in order to make it as accessible as possible (Ubuntu still
ships with darcs-1.0.9, and that's a fairly cutting edge
David Roundy wrote:
On Wed, Sep 17, 2008 at 4:46 PM, Ben Franksen
[EMAIL PROTECTED] wrote:
It often happens that I am looking for a patch in one branch of a project
that I maybe want to push into another branch. This could be a bug fix,
for instance. I know the patch in question affects
Wed Oct 1 22:18:38 CEST 2008 [EMAIL PROTECTED]
* fixed accidental merge of two lines in default boring
New patches:
[fixed accidental merge of two lines in default boring
[EMAIL PROTECTED] hunk ./src/Darcs/Repository/Prefs.lhs 134
\\.p_hi$, \\.p_o$, -- profiling Haskell
Hi All
a small question about --sendmail-command option to darcs send command: i
have problems with the patch bundle file: it's not there! I put this
send sendmail-command darcs-sendmail %a
into my ~/.darcs/defaults, and use this small test script as my
darcs-sendmail:
cp $1 huhu
When
Sorry, forgot to add output of 'darcs --version':
2.1.0pre3 (+ 13 patches)
Ben Franksen wrote:
a small question about --sendmail-command option to darcs send command: i
have problems with the patch bundle file: it's not there! I put this
send sendmail-command darcs-sendmail %a
into my
Thorkil Naur wrote:
[...]
Note here that the ls -ltr shows darcs244 existing, but darcs245 being
passed as the %a.
I'd call this a bug in darcs. I would be grateful if you could confirm and
report the issue to the darcs bug tracker.
Confirmed! See the new issue1128.
This shouldn't be too
Ben Franksen wrote:
Confirmed! See the new issue1128.
This shouldn't be too hard to fix.
...or so I thought. I find the code in Darcs.Command.Send resp
Darcs.Externals.hs very, ahem, hard to understand.
Anyway, I /think/ there is a problem in sendEmailDoc calling execSendmail,
because
Ben Franksen wrote:
Ben Franksen wrote:
Confirmed! See the new issue1128.
This shouldn't be too hard to fix.
...or so I thought. I find the code in Darcs.Command.Send resp
Darcs.Externals.hs very, ahem, hard to understand.
Anyway, I /think/ there is a problem in sendEmailDoc calling
Resending this patch. It's uncontroversial, I think.
Wed Oct 1 22:18:38 CEST 2008 [EMAIL PROTECTED]
* fixed accidental merge of two lines in default boring
New patches:
[fixed accidental merge of two lines in default boring
[EMAIL PROTECTED] hunk ./src/Darcs/Repository/Prefs.lhs 135
David Roundy wrote:
On Tue, Oct 07, 2008 at 05:51:34PM +0200, [EMAIL PROTECTED] wrote:
Resending this patch. It's uncontroversial, I think.
Wed Oct 1 22:18:38 CEST 2008 [EMAIL PROTECTED]
* fixed accidental merge of two lines in default boring
Content-Description: A darcs patch for
Tue Oct 7 13:53:03 CEST 2008 [EMAIL PROTECTED]
* resolve issue1128: must call execSendmail inside body of withOpenTemp
BTW: I have sent this with kmail (via a simple shell script). Yay!
New patches:
[resolve issue1128: must call execSendmail inside body of withOpenTemp
[EMAIL PROTECTED]
Tue Oct 7 20:52:33 CEST 2008 [EMAIL PROTECTED]
* fixed accidental merge of two lines in default boring; removed pattern for
directory dist
New patches:
[fixed accidental merge of two lines in default boring; removed pattern for directory dist
[EMAIL PROTECTED] hunk
Jason Dagit wrote:
On Tue, Oct 7, 2008 at 4:36 AM, [EMAIL PROTECTED] wrote:
Yes, this is ok, I was just confused. What is not ok is that execSendmail
gets called /outside/ the body of the withOpenTemp that creates the
attached file. That is, the file gets deleted before the sendmail command
Trent W. Buck wrote:
Ben Franksen [EMAIL PROTECTED] writes:
David Roundy wrote:
On Tue, Oct 07, 2008 at 05:51:34PM +0200, [EMAIL PROTECTED] wrote:
Resending this patch. It's uncontroversial, I think.
Wed Oct 1 22:18:38 CEST 2008 [EMAIL PROTECTED]
* fixed accidental merge of two lines
[EMAIL PROTECTED] wrote:
Sun Oct 12 01:41:48 CEST 2008 [EMAIL PROTECTED]
* cleanup default boring
Also turn default_boring and default_binaries into (pure) CAFs.
[I had a wrong defaults file, so 'darcs send' didn't ask me to edit the
description. Therefore the follow-up.]
I hope the
Florent Becker wrote:
our patch selection mechanism is very fine, but I feel it should give a
'last exit before hell question' at the end, so that you can review your
patch selection before commiting to whatever action it is you're
doing. Let me explain: suppose you are sending to a
Trent W. Buck wrote:
Ben Franksen [EMAIL PROTECTED] writes:
Sun Oct 12 01:41:48 CEST 2008 [EMAIL PROTECTED]
* cleanup default boring
Is refactor a more precise description than cleanup?
I prefer to use the term 'refactor' for changes that re-organize code, e.g.
by moving functionality
I found out about these two extensions by googling resp. searching
through the patch history (darcs annotate, obliterate, annotate,
obliterate,...).
BTW, the darcs-reannotate tool proved invaluable for this.
There are still 2 remaining regexes at the end of the list which are
undocumented.
If
David Roundy wrote:
On Tue, Oct 14, 2008 at 08:11:16AM -0400, David Roundy wrote:
On Tue, Oct 14, 2008 at 12:01:41PM +0200, [EMAIL PROTECTED]
wrote:
This is my previous patch amended to better reflect gnu arch's
funky file names. Thanks to Andy Smith for pointing me to the arch
wiki.
Eric Kow wrote:
The idea is that if I do:
runhaskell setup clean
ghc-pkg unregister mtl
runhaskell setup configure
runhaskell setup build
For some reason I thought the configure would pass and that the build
would fail. But I see this was an error, because actually the
Jason Dagit wrote:
On Fri, Oct 17, 2008 at 10:40 AM, Don Stewart [EMAIL PROTECTED] wrote:
darcs has more important battles to fight.
+1
We still don't have indentation patches! :)
Not to mention hunk movements (between files).
Cheers
Ben
Simon Michael wrote:
PS: I hate your quoting style (top posting, no trimming, spaces instead
of 's, blank line after every line).
PS: thanks for this report, and I hope you'll send more. I found your
quoting style a little hard to read, please consider following url to
help make us all more
Eric Kow wrote:
On Mon, Feb 02, 2009 at 20:31:39 +1100, Trent W. Buck wrote:
Under what circumstances is it desirable for a patch name to *not* be
a sentence?
Not all projects are prestigious and sometimes people just want to throw
together a quick little repository. I've also flip-flopped
Reinier Lamers wrote:
clean up Depends a wee tad
--
- Left e - throwError (MissingPatch (info hp) e)
+ Left e - Left (MissingPatch (info hp) e)
Does this make the code more obscure? I don't know how strong the
association
I /hope/ that there are no more cases where this issue can come up. It is
really hard to say, is_relative infects many other functions with its
partiality. In some of them I documented this by adding a clause that calls
'bug'. This should make it easier to to diagnose the problem if happens again.
Trent W. Buck wrote:
ben.frank...@online.de writes:
Sat Mar 28 00:18:21 CET 2009 ben.frank...@online.de
* Resolve issue1162: makeAbsolute is now a total function
AFAICT this should also move bugs/issue1162_add_nonexistent_slash.sh
into tests/.
I'll follow up with this. And some more
Ashley Moran wrote:
On 4 Apr 2009, at 16:23, Guillaume Hoffmann wrote:
When you edit the long comment with darcs amend-record
--edit-long-comment , the first line is in fact the name (or short
description) of the patch.
Thanks! I tested this and it works.
I find this really
Eric Kow wrote:
On Wed, Apr 01, 2009 at 13:26:01 -0700, Simon Michael wrote:
Eric/Petr thanks. The website has not automatically rebuilt, we need to
do something here. I tried /home/darcs-unstable/darcs$ make website
but no luck.
Here's the error I get:
darcs-unsta...@darcs:~/darcs$ make
Reviving an old discussion (as I am reading up on darcs-users)...
Eric Kow wrote:
On Thu, May 14, 2009 at 10:19:19 +0100, Simon Marlow wrote:
Yes, exactly. We want to work on branches and merge with the HEAD
regularly. Darcs doesn't support this well because:
- conflicts are painful to
Petr Rockai wrote:
PS: If the issue is in fact index-format-related, all those should go away
with beta 2, that will have proper index format detection/upgrade in it.
I'll test it with same repo as soon as beta 2 comes out.
Cheers
Ben
___
Eric Kow wrote:
On Mon, Jul 06, 2009 at 04:33:13 +0100, Robin Green wrote:
However, I know that darcs' patch theory allows patches to be
reordered. This could mean that the output of darcs query contents
--match=hash foo could vary over time - or have I misunderstood? Then,
if that's the
Hi
today I claimed to a co-worker that (of course!) windows binaries for the
latest darcs release are readily available for download. To my great
embarrassment I was proven wrong: the link from the darcs home page
(Pre-built Darcs binaries ...) leads to a place on the wiki where only
binaries for
Florent Becker wrote:
Reinier Lamers wrote:
These changes offer some useful functionality, but they do suffer from
the problems inherent in the current [DarcsFlag] paradigm of command line
handling. It seems that when you specify both --quiet and --verbose, you
get the debug output but not
Dan Pascu wrote:
On 3 Oct 2009, at 14:21, Ben Franksen wrote:
Florent Becker wrote:
Reinier Lamers wrote:
These changes offer some useful functionality, but they do suffer
from
the problems inherent in the current [DarcsFlag] paradigm of
command line
handling. It seems that when you
Eric Kow wrote:
On Mon, Oct 05, 2009 at 14:28:29 +0100, Sittampalam, Ganesh wrote:
With just --don't-allow-conflicts, conflicting patches are presented
during interactive selection, but selecting one causes a later failure.
With just --skip-conflicts, conflicting patches are not presented
Jason Dagit wrote:
It's possible that regex-pcre gives better performance than regex-posix
I made some tests using the new criterion package (excellent for stuff like
that) and found regex-pcre to be faster by a factor of 3 to 9, depending on
regex and test string. I did not test it with darcs,
Jason Dagit wrote:
benjamin.frank...@bessy.dewrote:
Jason Dagit wrote:
It's possible that regex-pcre gives better performance than regex-posix
I made some tests using the new criterion package (excellent for stuff
like that) and found regex-pcre to be faster by a factor of 3 to 9,
Jason Dagit wrote:
On Mon, Oct 5, 2009 at 6:25 PM, Trent W. Buck
t...@cybersource.com.auwrote:
Ben Franksen benjamin.frank...@bessy.de writes:
Jason Dagit wrote:
It's possible that regex-pcre gives better performance than
regex-posix
I made some tests using the new criterion package
Ben Franksen wrote:
Sure, file is attached.
This is the output on my machine at home:
b...@sarun[2]: ~/tmp uname -a
Linux sarun 2.6.24-24-generic #1 SMP Sat Aug 22 01:06:14 UTC 2009 i686
GNU/Linux
b...@sarun[2]: ~/tmp ghc --make regexbench.hs
[1 of 1] Compiling Main
Sittampalam, Ganesh wrote:
Dan Pascu wrote:
On 5 Oct 2009, at 22:51, Ganesh Sittampalam wrote:
If they are mutually exclusive, I assume that the program will
decide what option to use before it starts to do anything. So if I
have skip-conflicts in the defaults file but I give --dont-allow-
Eric Kow wrote:
This came up during benchmarking. It's a bit hard to talk about
benchmarking because one has to understand our version scheme where
- darcs 2.3.97.x refers to darcs 2.4 alpha x
- darcs 2.3.98.x refers to darcs 2.4 beta x
- darcs 2.3.99.x refers to darcs 2.4 rc x
Jason Dagit wrote:
On Thu, Feb 25, 2010 at 10:35 AM, Ben Franksen
benjamin.frank...@bessy.dewrote:
Reinier Lamers wrote:
I want to let you know that I am beginning to work on the final 2.4
release, which would then happen some time this weekend. Compared to
2.3.99.2, this would contain
Reinier Lamers wrote:
I want to let you know that I am beginning to work on the final 2.4
release, which would then happen some time this weekend. Compared to
2.3.99.2, this would contain the remove-nonempty-directory (issue1749) fix
as the only extra patch.
If I have again skimmed over a
I realize that the output talks about 'apply', not push, but anyway this
seems inconsistent to me. Note that I have not done 'darcs apply' in the
first place. (Yes, I know that push is the same as send+apply. Still.)
My suggestion is that push should support at least one of these options.
(Why
Eric Kow wrote:
On Wed, May 05, 2010 at 21:35:29 +0200, Ben Franksen wrote:
I realize that the output talks about 'apply', not push, but anyway this
seems inconsistent to me. Note that I have not done 'darcs apply' in the
first place. (Yes, I know that push is the same as send+apply. Still
Eric Kow wrote:
On Wed, May 05, 2010 at 23:07:09 +0200, Ben Franksen wrote:
I think you want http://bugs.darcs.net/issue1429
Yes, sorry I was too lazy to first check the bug tracker. Anyway, the
ticket does not mention that these options are recommended by darcs when
doing a push, this IMO
Hello Darcsers
a few days ago I started converting a Subversion repo to Darcs. This did not
go very smoothly. I used tailor as this seems to be the only existing tool
for the job.
The conversion process went fine, however
(1) tailor ignores svn tags: they do not appear as darcs tags in the
Gour wrote:
On Fri, 07 May 2010 21:01:24 +0200
Ben == Ben Franksen benjamin.frank...@bessy.de wrote:
Ben I tried to convert via other VCSes (bzr,hg). Conversion to bzr
Ben added the tags just fine, so I thought maybe tailor can convert
Ben from the bzr repo.
If you were able to convert
Ben Franksen wrote:
Gour wrote:
On Fri, 07 May 2010 21:01:24 +0200
Ben == Ben Franksen benjamin.frank...@bessy.de wrote:
Ben I tried to convert via other VCSes (bzr,hg). Conversion to bzr
Ben added the tags just fine, so I thought maybe tailor can convert
Ben from the bzr repo.
If you
Lele
I am sorry if I sounded grumpy and demanding. This was not what I intended,
but I see that it has come out like that. Fact is, I *am* glad and thankful
for the work you did with tailor. Without tailor I would never have had the
opportunity to establish Darcs at where I work. And, BTW, I
Eric Kow wrote:
On Thu, Aug 12, 2010 at 10:46:02 +0200, Benjamin Franksen wrote:
'darcs rollback' seems to offer only patches that are not depended upon
by other patches in the same repo. I don't understand the reason for this
limitation. If someone could enlighten me I'd be grateful.
Are
Ben Franksen wrote:
Eric Kow wrote:
On Thu, Aug 12, 2010 at 10:46:02 +0200, Benjamin Franksen wrote:
'darcs rollback' seems to offer only patches that are not depended upon
by other patches in the same repo. I don't understand the reason for
this limitation. If someone could enlighten me I'd
Ian Lynagh wrote:
On Thu, Aug 12, 2010 at 10:12:19PM +0200, Ben Franksen wrote:
No, I was using interactive UI. The patch (call it A) I wanted to
rollback had another patch (call it B) depending on it. B was offered by
'darcs rollback' and when I said 'n[o]' (because I want to rollback
Alexey Levan wrote:
2010/8/23 Eric Kow ko...@darcs.net:
On Fri, Aug 20, 2010 at 14:17:41 +0200, Benjamin Franksen wrote:
darcs changes xxx
Changes to MotorApp/docu/xxx:
Tue Aug 19 14:30:36 CEST 2008 bernhard.ku...@bessy.de
* Converted from 3.13 (MotorApp)
Sounds like
Guillaume Hoffmann wrote:
The user impression is that darcs is failing and there is some support
for the old format, but very incomplete.
Darcs could print an informative message explaining exactly this.
It is just a matter of updating the message it is already printing
when getting from OF
Petr Ročkai wrote:
darcs-ADV annotate src/test.hs 0,08s user 0,01s system 93% cpu 0,102 total
1: Wed Jul 7 20:06:00 CEST 2010 Ganesh Sittampalam gan...@earth.li
* move main unit testing code into module with proper name (not Main)
This is enable other things than the unit executable to
This is completely off-topic, but your link
Eric Kow wrote:
* conflict marking should tell you which patches the sides
of the conflict come from
http://bugs.darcs.net/isuse833
triggered a bug in the tracker. Note the typo (isuse instead of issue). I
get
MOD_PYTHON ERROR
ProcessId:
Occasionally, it would be extremely helpful to have a bit more context when
recording changes to a file (hunks). What I would like to have then, is a
key that list the hunk with a few lines of context before and after the
hunk. For concreteness, let me make this proposal more concrete:
For each
Benjamin Franksen wrote:
Benjamin Franksen wrote:
Sittampalam, Ganesh wrote:
Benjamin Franksen wrote:
Benjamin Franksen wrote:
darcs: stdin: hIsTerminalDevice: illegal operation (handle is
closed) Apply failed!
This is most mysterious. I removed all occurrences of hIsTerminalDevice
from
Reinier Lamers wrote:
There is a new packager's preview tarball:
http://reinier.de/darcs/darcs-2.5- packrelease2.tar.gz . People making
binary distributions of darcs releases can use this tarball to make a
binary that can be distributed as a darcs 2.5 binary if darcs 2.5 is
released next
I seem to be the one who has problems with the darcs-2.5 beta (2.4.99.1).
It now happened to me that I have made lots of small changes to a project
and cannot record them because darcs record takes 'forever' to complete. I
can upload the repo and my unrecorded changes, just tell me where. The tar
Ben Franksen wrote:
I seem to be the one who has problems with the darcs-2.5 beta (2.4.99.1).
It now happened to me that I have made lots of small changes to a project
and cannot record them because darcs record takes 'forever' to complete.
Ok folks, it seems something was broken with my
Ganesh Sittampalam wrote:
Hi Simon,
On Thu, 25 Nov 2010, Simon Marlow wrote:
$ darcs pull ~/darcs/ghc-testing/libraries/base
Note: if you want to change the default remote repository to
/home/simonmar/darcs-all/work/ghc-testing/libraries/base,
quit now and issue the same command with the
Hi Darcsers
when a few versions ago 'darcs changes' aquired the --interactive switch I
immediately put 'changes interactive' in my ~/.darcs/default, so now I say
just 'darcs changes' to view the last few patches. It now happened to me for
the n-th time that I wished I could select another
Hi Wolfgang
I agree wholeheartedly and would very much like a switch to turn on relative
path names, as you propose. Please list me as supporter if you create a
ticket.
Cheers
Ben
Wolfgang Dobler wrote:
I haven't found an existing bug for the following, seemingly natural,
feature request:
Will 2.8 contain rebase?
Ben
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Michael Hendricks wrote:
I suspect that 2.8 will not contain rebase. The associated issue
hasn't been updated in almost 2 years: http://bugs.darcs.net/issue938
The package darcs-beta on Hackage doesn't seem to have rebase
functionality and I see no mentions of rebase in the screened
Archi wrote:
On Sat, 25 Feb 2012 07:21:00 -0700, Stephen J. Turnbull
step...@xemacs.org wrote:
Archi writes:
What scenario were you wanting rebase for that patch commutation does
not
solve? There are specific corner cases, but I don't see how cornercases
make for a good marketing
Michael Hendricks wrote:
On Sat, Feb 25, 2012 at 7:21 AM, Stephen J. Turnbull step...@xemacs.org
wrote:
Archi writes:
What scenario were you wanting rebase for that patch commutation does
not solve? There are specific corner cases, but I don't see how corner
cases make for a good
Hi Experts
I recently had a situation where I could not apply a patch bundle created
using darcs send because darcs apply complained about a missing patch in the
repo. So I pulled the missing patch, could apply the bundle, and then
obliterated the patch I just pulled. So, obviously the bundle
Hi Eric
thanks for explaining and adding the FAQ entry.
Eric Kow wrote:
On 3 Mar 2012, at 07:08, Eric Kow wrote:
On 3 Mar 2012, at 02:30, Ben Franksen wrote:
I recently had a situation where I could not apply a patch bundle
created using darcs send because darcs apply complained about
Eric Kow wrote:
On 4 Mar 2012, at 12:28, Ben Franksen wrote:
As far as I am concerned, the 'darcs send computes minimal context'
solution would be perfect. But I have no idea how difficult that is (both
for the darcs developers and then for darcs). For a compromise, maybe
some approximation
Ganesh Sittampalam wrote:
On 05/03/2012 17:05, Owen Stephens wrote:
On 5 March 2012 16:18, Michael Hendricks mich...@ndrix.org
mailto:mich...@ndrix.org wrote:
Since I'm not yet familiar with Darcs' internal workings, can someone
help me understand why calculating a minimal context is so
Michael Hendricks wrote:
- suspend and unsuspend
[...]
- need a way to list suspended patches (darcs changes --suspended?)
Yes.
- pull
- should be darcs pull --suspend-conflicts
- even better would be darcs pull
Ben Franksen wrote:
Florent Becker wrote:
The darcs team is pleased to announce the release of darcs 2.7.99.1, aka
2.8 rc 1, the first release candidate for darcs 2.8.
I get many many warnings during teh build (using ghc-7.0.4 from my distro).
This was not the case when I compiled the last
Owen Stephens wrote:
On 2 April 2012 21:59, Ben Franksen benjamin.frank...@bessy.de wrote:
I get many many warnings during teh build (using ghc-7.0.4 from my
distro).
This was not the case when I compiled the last beta.
Various changes that were made before the beta introduced
Hi Michael
Michael Hendricks wrote:
- rewording commit messages, changing author, changing date, etc
- amend-record does this, it's just not smart enough yet
- rewording a patch needs no commute operations
- dependencies should never prevent a reword operation
Florent Becker wrote:
- Darcs now supports multiple email addresses for the author in
the global prefs file. So, if you use different identities for
home and work, you can now easily select between them.
(issue1530)
Which global prefs file is that? I see no mention of such a file in the
Eric Kow wrote:
On 30 Apr 2012, at 23:05, Michael Orlitzky wrote:
Maybe use some other repo for the hello world example?
$ darcs get http://darcs.net darcs
Agreed
It would be great if somebody could help flesh out a
http://darcs.net/hello/
Ideas:
- the text files in here could
Eric Kow wrote:
On 8 May 2012, at 20:06, Ben Franksen wrote:
Florent Becker wrote:
- Darcs now supports multiple email addresses for the author in
the global prefs file. So, if you use different identities for
home and work, you can now easily select between them.
(issue1530)
Which
Simon Michael wrote:
On 5/8/12 12:13 PM, Ben Franksen wrote:
I like the new home page with the quick start examples and news etc. But
may I humbly suggest not to use fixed widths for the two columns of the
front page, but rather adapt (mostly the left column) to the user's
window size? If I
Owen Stephens wrote:
On 18 July 2012 14:45, Benjamin Franksen
benjamin.frank...@helmholtz-berlin.de wrote:
A long-time issue I have with darcs is that I cannot use read-only
repositories, even with commands that -- semantically speaking -- do not
change the repository, such as 'darcs
Aditya wrote:
Patch index improves the speed of changes and annotate commands by
quickly
identifying the patches that modified a given file. This optimization
is especially useful for large repositories.
How large is the expected gain? Can you share some performance numbers, i.e.
Ben Franksen wrote:
Aditya wrote:
One of the concerns I already have is automatic creation of patch index
on
existing repositories. The time it takes to create patch index increases
dramatically based on buffer
cachehttp://oss.sgi.com/LDP/LDP/sag/buffer-cache.html.
Creating a patch index
Miles Gould wrote:
On 03/08/12 07:18, Eric Kow wrote:
We could do so. How would having a separate command (as opposed to a
flag) be beneficial in your view?
I for one would be confused by a send command that doesn't send
anything - both when trying to figure out the behaviour of darcs send
For whatever reason I cannot login to the bug tracker, so I send this bug
report here.
The (obviously wrong) error message in the subject appears when I have
obliterate output-auto-name
in my ~/.darcs/defaults and I try to 'darcs obliterate'.
darcs obliterate
darcs: Bad default
Joshua Tilles wrote:
I'd been looking for something with which to explore using Darcs, and
right now I'm trying to set up using Darcs on my dotfiles. I really like
Eli Barzilay's
approachhttp://www.xxeo.com/archives/2010/02/16/dotfiles-in-git-finally-
did-it.html/comment-page-1#comment-126903
be readable and
writeable only by the owner. Etc etc.
Cheers
Ben
Ben Franksen wrote:
Joshua Tilles wrote:
I'd been looking for something with which to explore using Darcs, and
right now I'm trying to set up using Darcs on my dotfiles. I really like
Eli Barzilay's
approachhttp://www.xxeo.com
Gabriel Kerneis wrote:
On Wed, Aug 15, 2012 at 01:18:28PM +0100, Eric Kow wrote:
As I currently understand the situation, the
default-configed-mailer-I-didn't-even-know-was-there *thinks* it
succeeded. So I suppose we need some way of gathering extrinsic evidence
that the send worked (and
1 - 100 of 142 matches
Mail list logo
