On Mon, Mar 10, 2008 at 5:37 PM, Mark Stosberg [EMAIL PROTECTED] wrote:
I know that as potential hacker I'm turned off when I see lines like this:
wspfr _ _ NilRL _ = return Nothing
wspfr jn matches (p::pps) skipped
( from SelectChange.lhs, line 183)
In the programming culture I come
On Wed, Mar 5, 2008 at 11:59 AM, David Roundy [EMAIL PROTECTED] wrote:
Hi all,
Our macos buildbot (see http://darcs.net:8008/) is hanging when running
steve_and_monica_rollback.sh. I've no desire to track this down via the
buildboby pushing printf-style debug tests to the central
On Tue, Mar 4, 2008 at 8:27 PM, Josh Wilcox [EMAIL PROTECTED] wrote:
New submission from Josh Wilcox [EMAIL PROTECTED]:
Because darcs does not handle backspace in the expected way when I find it
almost impossible to add reasonable patch names. This is extremely
irritating.
What is it
On Feb 16, 2008 10:40 AM, Eric Y. Kow [EMAIL PROTECTED] wrote:
Hi Jason,
This patch seems to make list_authors and darcs changes hang on my
macbook. Any ideas?
I made a copy of my working repo, reverted everything back to where
this patch was on the top, compiled and ./list_authors and
On Fri, Feb 15, 2008 at 10:58 AM, David Roundy [EMAIL PROTECTED] wrote:
On Fri, Feb 15, 2008 at 10:18:04AM -0800, Jason Dagit wrote:
Sun Feb 10 01:00:34 PST 2008 Jason Dagit [EMAIL PROTECTED]
* make Hopefully have type witnesses
Thanks! This looks good, but I've got one question
This is an amended version of the previous refactor to Hopefully.
Hopefully this one is better? :)
Thanks,
Jason
Fri Feb 15 12:31:30 PST 2008 Jason Dagit [EMAIL PROTECTED]
* make Hopefully have type witnesses
New patches:
[make Hopefully have type witnesses
Jason Dagit [EMAIL PROTECTED
On Thu, Feb 14, 2008 at 5:39 PM, Mark Stosberg [EMAIL PROTECTED] wrote:
Jokes aside, I think you have the addresses right. However, I noticed if
I type them into Firefox, they don't seem to work, but when I darcs
pull, they seem to.
I seem to be banging my head against issue692. I can fix
Fri Feb 8 10:41:26 PST 2008 Jason Dagit [EMAIL PROTECTED]
* Make HashedIO.lhs compile with type witnesses
Fri Feb 8 10:41:49 PST 2008 Jason Dagit [EMAIL PROTECTED]
* Add Depends and HashedIO to witnesses in make file
New patches:
[Make HashedIO.lhs compile with type witnesses
Jason
On Feb 8, 2008 5:34 PM, Jason Dagit [EMAIL PROTECTED] wrote:
Fri Feb 8 17:32:15 PST 2008 Jason Dagit [EMAIL PROTECTED]
* make Cache p work with type witnesses
I think this last one does the wrong thing. For some reason if a type
signature starts with:
RepoPatch p = Cache p
Then I have
New submission from Jason Dagit [EMAIL PROTECTED]:
The main darcs webpage at http://darcs.net does not immediately show you where
to get access to the darcs source repositories.
Furthermore, http://darcs.net/repos is not browse-able making it harder to
discover the repositories
Quick and dirty hack to add links to the darcs.net webpage.
Please edit as needed.
Thanks,
Jason
Thu Feb 7 14:41:20 PST 2008 Jason Dagit [EMAIL PROTECTED]
* Add links to darcs repositories to main webpage
New patches:
[Add links to darcs repositories to main webpage
Jason Dagit [EMAIL
Thu Feb 7 14:17:06 PST 2008 Jason Dagit [EMAIL PROTECTED]
* amended Depends.lhs for type witnesses
New patches:
[amended Depends.lhs for type witnesses
Jason Dagit [EMAIL PROTECTED]**20080207221706] {
hunk ./src/Darcs/Patch/Depends.lhs 421
\end{code}
\begin{code}
-commute_to_end
On Feb 6, 2008 8:48 AM, David Roundy [EMAIL PROTECTED] wrote:
On Wed, Feb 06, 2008 at 11:44:42AM -0500, David Roundy wrote:
Maybe we can egg on the bytestring people and get them to submit
patches taking this further down (for example, they could improve our
between newlines and nth
On Feb 6, 2008 9:24 AM, Eric Kow [EMAIL PROTECTED] wrote:
New submission from Eric Kow [EMAIL PROTECTED]:
It would be really useful to have a quick and dirty benchmarking script that
we
can either distribute with or alongside darcs
The script would just encode some current darcs
Sorry,
I guess my last compile/testrun with type witnesses didn't happen. I
just noticed a compile error in Depends.lhs.
Please ignore this patch as it will be superseded by a correct one
amend-recorded one.
Thanks,
Jason
On Feb 6, 2008 2:16 PM, Jason Dagit [EMAIL PROTECTED] wrote:
Wed Feb
On Feb 5, 2008 6:43 AM, David Roundy [EMAIL PROTECTED] wrote:
On Mon, Feb 04, 2008 at 09:05:55PM -0800, Jason Dagit wrote:
On Feb 4, 2008 4:30 PM, Dmitry Kurochkin [EMAIL PROTECTED] wrote:
Some fixes and cleanups for configure checks.
And fix for copyRemotesNormal - if we use
On Feb 4, 2008 10:30 AM, Alexander Staubo [EMAIL PROTECTED] wrote:
I would love to see someone use kernel facilities such as FSEvents [1]
on OS X and inotify [2] on Linux to accomplish this. (There are also
others such as fam [3], and Windows has its own easy-to-use API.)
I remember someone
On Feb 4, 2008 4:30 PM, Dmitry Kurochkin [EMAIL PROTECTED] wrote:
Some fixes and cleanups for configure checks.
And fix for copyRemotesNormal - if we use copyUrlFirst the first patch
is downloaded last. So we lock in waitUrl and progress indication stops.
On a similar note, how can we make
Conflictors are no more and it seems their repository disappeared as
well. No one was sure how to really solve the problems using
conflictors. We're now knee deep in a different approach that we
refer to as 'conflict handling'. We're adding cancellation patches
and conflicted patches. Patches
On 8/3/07, Simon Marlow [EMAIL PROTECTED] wrote:
David Roundy wrote:
On Wed, Aug 01, 2007 at 01:58:29AM +0100, Ian Lynagh wrote:
And the cancel A patch doesn't have any sort of reference to B in it?
Right.
I seem to remember there was a problem with this approach. Perhaps not a
Fantastic analysis. Exactly what I was looking for. I'm now convinced :)
The icing on the cake would be to check this on various platforms but
I'm convinced enough already.
Thanks!
Jason
On 7/30/07, Kevin Quick [EMAIL PROTECTED] wrote:
On Sat, 28 Jul 2007 17:23:13 -0700, Jason Dagit
[EMAIL
On 7/18/07, Kevin Quick [EMAIL PROTECTED] wrote:
Presumably it's faster to let the System.Directory.copyFile perform
the file copying than working through the PackedString and the IO monad.
My testing didn't show any real timing difference, but it may have less
effect on memory/GC issues and
On 7/12/07, Stefan O'Rear [EMAIL PROTECTED] wrote:
On Fri, Jul 13, 2007 at 01:55:26AM +0200, Juliusz Chroboczek wrote:
The fact that this problem occurs rather often suggests that there are
serious issues with darcs as it stands.
I think we are all aware of that. In its current state,
).
Thanks,
Jason
On 7/10/07, Jason Dagit [EMAIL PROTECTED] wrote:
Hello,
Here is the new merge algorithm that works with conflicts by
creating 'conflicted' patches to store the conflicts in as
they are discovered.
I hadn't been showing this off yet, because I'm not sure if
it really is order independent
from ghc).
Thanks,
Jason
Simon
| -Original Message-
| From: Ian Lynagh [mailto:[EMAIL PROTECTED]
| Sent: 15 June 2007 15:53
| To: Jason Dagit
| Cc: [EMAIL PROTECTED]; darcs-devel@darcs.net; Simon Peyton-Jones
| Subject: Re: [darcs-devel] advice on GADT type witnesses needed
|
| On Thu, Jun
On 6/16/07, David Roundy [EMAIL PROTECTED] wrote:
I hope that's clear. I know it's pretty brief. My implementation actually
uses unsafeCoerce# internally when parsing Conflicted patches. We could
have avoided this by storing the inverse of the conflicted patch and its
context, but it didn't
On 6/14/07, Eric Y. Kow [EMAIL PROTECTED] wrote:
Would the loss of this functionality be acceptable if darcs had some
kind of extra verbose mode, where it printed out all the patches it was
trying to get? Or would calling wget still be useful/more flexible for
other reasons?
I'm a huge fan of
On 6/14/07, David Roundy [EMAIL PROTECTED] wrote:
src/Darcs/Patch/Show.lhs:50:0:
Quantified type variable `y' is unified with another quantified type
variable `x'
When trying to generalise the type inferred for `showPatch'
Signature type: forall x y. Patch x y - Doc
Hello!
On 6/11/07, Samuel A. Falvo II [EMAIL PROTECTED] wrote:
I don't mean to whack a hornet's nest here, but recently I've had a
very disturbing issue with darcs where it corrupted its repository on
a company project. I found myself in a situation where I needed to
fork a single project and
On 6/4/07, Ganesh Sittampalam [EMAIL PROTECTED] wrote:
On Wed, 30 May 2007, Jason Dagit wrote:
As you may know, I'm part of an effort to improve conflict handling in
darcs. We have come up with a plan that allows users to cancel and
activate patches (more on this later). Implementing
Thank you very much for the questions. Hopefully David will comment
about the name patches (below) or on any mistakes I've made.
On 5/30/07, Ian Lynagh [EMAIL PROTECTED] wrote:
On Wed, May 30, 2007 at 03:49:35PM -0700, Jason Dagit wrote:
2) An activation patch should never modify other
Hello,
After what seems like an eternity of bumbling with patch theory and a
lot of help from David, I've implemented activation patches as a new
patch type in darcs.
Below is a description of what I learned, what I did, and why. I hope
that by describing what I learned others can begin
On 12/9/06, David Roundy [EMAIL PROTECTED] wrote:
Hi all,
I've just started (an hour ago) converting all the (PatchInfo, Maybe Patch)
instances in darcs to (PatchInfo, Hopefully Patch) where
data Hopefully a = Actually a | Unavailable String
Is there a reason to not use 'Either a String'
On 12/9/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
On Sun, Dec 10, 2006 at 00:33:07 +0100, Tommy Pettersson wrote:
Just a thought: debian will have GHC 6.6 in their next release,
so we could possibly skip 6.4 support (when we drop 6.2).
That would make life so much simpler. It would give us a
Hello,
Recently, I was inspired by Donald Stewart to create a plot of # of
patches contributed by darcs contributors. I borrowed a gnuplot
script from Don and created this:
http://files.codersbase.com/commiters-2006-12-08.png
It's not yet automated but it shouldn't be too hard to automate if
On 12/3/06, David Roundy [EMAIL PROTECTED] wrote:
Hi all,
Here's a change in behavior that I think will be an improvement. The
current behavior has bitten me once, scattering a repository directly into
my home directory, which was quite a pain.
I agree this new behavior is better than the
Josh,
This should be fairly easy to implement.
Modify test_patch in Test.lhs so that it checks for
--ask-record-on-failed-test (or whatever sounds good). Also look at
ArgumentDefault.lhs, DarcsArguments.lhs, DarcsCommand.lhs and
DarcsFlags.lhs to get a feel for how to implement the commandline
We have a developer FAQ
http://darcs.net/DarcsWiki/DeveloperFAQ
And some developer Tips
http://darcs.net/DarcsWiki/DeveloperTips
You're right that we should probably say something about tabs, but on
the other hand with the test suite checking for it gets found right
away for most people :)
And
Sat Nov 4 13:47:49 PST 2006 Jason Dagit [EMAIL PROTECTED]
* add HACKING file
New patches:
[add HACKING file
Jason Dagit [EMAIL PROTECTED]**20061104214749] {
addfile ./HACKING
hunk ./HACKING 1
+For more information about darcs hacking and best practices please check
+the darcs wiki at http
On 10/8/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
On Sat, Sep 30, 2006 at 15:13:06 +0200, Eric Kow wrote:
Sat Sep 30 14:10:32 CEST 2006 Eric Kow [EMAIL PROTECTED]
* Require 'permission denied' test for MacOS X again.
Nobody complained, so it's going in.
I just verify that on my machine
On 10/2/06, Dino Morelli [EMAIL PROTECTED] wrote:
Also, I see a lot of underscore-style functions like
get_long_darcs_opt_string. Is there a naming preference for this project?
I can only speak for myself, but I'd say no underscores. I prefer
camel case for Haskell code. Others?
Working on
Simon,
What does 'darcs --exact-version' say? I just want to make sure you
don't have a terribly old darcs here.
Thanks,
Jason
On 9/29/06, simonpj [EMAIL PROTECTED] wrote:
New submission from simonpj [EMAIL PROTECTED]:
Dear Darcsers,
It's not my day.
I recorded patch, but by mistake gave
On 9/13/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
Also, another patch which I would be interested in is one that adds
tests for the mechanism. What tests exactly, I'm not entirely sure.
Some examples might be making sure that ignored files really are
ignored, that there aren't any weird
On 9/11/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
What do people think?
What actual problem are you trying to solve?
To quote myself:
I was working on the darcs source today and I realized that in a lot
of ways the current logging output is poor. Mostly we don't have
enough of it.
On 9/11/06, David Roundy [EMAIL PROTECTED] wrote:
On Sun, Sep 10, 2006 at 04:12:28PM -0700, Jason Dagit wrote:
Hello,
I was working on the darcs source today and I realized that in a lot
of ways the current logging output is poor. Mostly we don't have
enough of it.
Here are some changes
On 9/11/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
I'd rather avoid putting an Int into verbose, as in my experience this
makes it hard to keep consistent levels of verbosity than otherwise.
I'd go with something more like
I have no opinion on whether having multiple levels of verbosity is a
On 9/11/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
On Mon, Sep 11, 2006 at 14:17:30 -0700, Jason Dagit wrote:
Although I hadn't mentioned it yet, I was actually hoping that at some
point in the distance future we may extend the IO monad to carry
around some extra details and at that time logStr
On 9/9/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
On Sat, Sep 09, 2006 at 22:10:14 +0200, Tommy Pettersson wrote:
Anyway, I had some difficulty reading the code (most of the code
in Exec.lhs), so I tried to make it more readable, which (for me
at least) means more simple. So I only kept one
Fri Sep 8 10:09:47 PDT 2006 Jason Dagit [EMAIL PROTECTED]
* whatsnew --look-for-adds doesn't read unadded files (fix for issue79)
Changes darcs whatsnew --look-for-adds to by default stop computing the patch
for a while when it realizes the file is not managed by darcs. This matches
On 9/8/06, Tommy Pettersson [EMAIL PROTECTED] wrote:
On Fri, Sep 08, 2006 at 10:26:07AM -0700, Jason Dagit wrote:
Fri Sep 8 10:09:47 PDT 2006 Jason Dagit [EMAIL PROTECTED]
* whatsnew --look-for-adds doesn't read unadded files (fix for issue79)
Changes darcs whatsnew --look-for-adds
On 8/24/06, Edwin Thomson [EMAIL PROTECTED] wrote:
Hello
I'm finding darcs's diff command to be unusably slow for large
repositories, so I'm trying to speed it up. Darcs seems to do diff by
making two copies of the repository, with different patches applied on
each, which results in a lot of
On 8/22/06, Jonathon McKitrick [EMAIL PROTECTED] wrote:
New submission from Jonathon McKitrick [EMAIL PROTECTED]:
Not sure how this happened, but I was running 1.0.2.
You should definitely consider upgrading. 1.0.2 - 1.0.8 fixes a lot
of bugs and dramatically improves performance.
I hit
On 4/23/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
Juliusz and I have talked a bit about how we can modify the current
setup to work well with the darcs development style. We did
mention a way to keep the webpage in sync with the repository,
Just as a side note -- some of you may
On 8/2/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
Some initial comments:
On Wed, Aug 02, 2006 at 18:14:40 -0700, Nathaniel Gray wrote:
Aside from some aesthetic objections, the only serious problem I see is
that changing the method used to execute the posthook from
System.Cmd.system to
On 8/2/06, Nathaniel Gray [EMAIL PROTECTED] wrote:
Jason Dagit wrote:
On 8/2/06, Eric Y. Kow [EMAIL PROTECTED] wrote:
Some initial comments:
On Wed, Aug 02, 2006 at 18:14:40 -0700, Nathaniel Gray wrote:
Aside from some aesthetic objections, the only serious problem I see is
that changing
Sure, that gives everyone a chance to read it.
BTW, there is some documentation on how to keep your maintainer happy.
Here are a few links just in case you didn't see it already:
http://darcs.net/pipermail/darcs-devel/2006-January/003934.html
http://darcs.net/DarcsWiki/DeveloperFAQ
I would rather not see this mailing list turn into a debate forum for
political/social/economic/legal issues (unless they are very directly
related to darcs, such as what license darcs should be released
under).
Please continue this discussion elsewhere.
Thank you for your cooperation.
Jason
On 5/21/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Dear David Roundy and darcs-devel:
[snip]
Therefore, I would like to ask permission from you, the authors of darcs, to
combine darcs with openssh, Eclipse, and SWT. I hereby ask the copyright
holders to grant me permission to use the
On 5/14/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
Sun May 7 18:30:09 CEST 2006 Eric Kow [EMAIL PROTECTED]
* Tidy up comment for working dir in patch apply.
+-- | Note: The expression (@apply flags working p@) applies the patch
+-- to whatever directory-like monad you are in. If
I haven't tested the patch, but the code looks clean and I look
forward to a feature like this.
But I have some questions.
How general is this approach? It looks like you've added this 'check'
in one place so far. Do you think you could generalize this to a
prehook? That is, all commands can
FWIW, upgrading from ghc 6.4 - 6.4.1 fixed the problem when I
reported it for OSX.
Thanks,
Jason
On 4/28/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
-import DarcsRepo ( seekRepo, youNeedToBeInRepo )
According to Don Stewart,
This was a ghc 6.4.0 buglet. Its fixed in ghc 6.4.1
Please
I second this suggestion.
On 4/24/06, Jonathan Daugherty [EMAIL PROTECTED] wrote:
New submission from Jonathan Daugherty [EMAIL PROTECTED]:
It would be really great if one could set DARCS_PAGER=/path/to/pager to be
used
when reviewing patches interactively in record and whatsnew modes (and
On 4/22/06, Tommy Pettersson [EMAIL PROTECTED] wrote:
On Thu, Apr 20, 2006 at 10:56:09PM -0700, Jason Dagit wrote:
1) How many bytes do line endings add to the length of the old or new
content? Is it okay to assume line endings are exactly one byte in
patches? I know this will hold
On 4/22/06, Ian Lynagh [EMAIL PROTECTED] wrote:
[replying to 2 messages in one]
On Sat, Apr 22, 2006 at 10:15:07AM -0700, Jason Dagit wrote:
I found some time tonight to start implementing a different format for
hunks. Very simple but meant to allow skipping over data.
hunk filename
On 4/18/06, Travis Cross [EMAIL PROTECTED] wrote:
Jason Dagit wrote:
On 4/7/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
This is a resend of my previous patch, reduced to only hack umasks.
The functionality of Uid and Gid is better handled with the sgid directory
hack.
Sat Mar 25
Hello,
It seems that the darcs wiki is down. When I visit the wiki I get a
diagnostics page that begins with the error:
IOError[Errno 122] Disk quota exceeded
Thanks,
Jason
___
darcs-devel mailing list
darcs-devel@darcs.net
On 4/7/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
This is a resend of my previous patch, reduced to only hack umasks.
The functionality of Uid and Gid is better handled with the sgid directory
hack.
Sat Mar 25 20:06:22 CET 2006 Juliusz Chroboczek [EMAIL PROTECTED]
* Propagate opts to
I don't know what happened to this patch so I'm resubmitting a version against
darcs-unstable.
Thanks,
Jason
Sat Apr 15 20:14:33 PDT 2006 Jason Dagit [EMAIL PROTECTED]
* added make target for generating api-docs
Sat Apr 15 20:26:02 PDT 2006 Jason Dagit [EMAIL PROTECTED]
* corrections
On 3/22/06, Zachary P. Landau [EMAIL PROTECTED] wrote:
On 3/22/06, Jason Dagit [EMAIL PROTECTED] wrote:
On 3/22/06, Zachary P. Landau [EMAIL PROTECTED] wrote:
Anyway I set this up so people can get a feel for it and see if they like
it.
If it isn't found to be very useful, I'll take
On 4/15/06, Zachary P. Landau [EMAIL PROTECTED] wrote:
A step behind that is to have someone interested enough to mark when a
patch ends up in the stable and unstable branches.
I guess the final goal would be having the repository maintainers mark
patches
as being
I just grabbed a fresh copy of the latest unstable and tried to
compile but I get these messages:
$ make
ghc -cpp -package QuickCheck -package util -package parsec -O
-funbox-strict-fields -Wall -Werror -I. -DHAVE_CURSES -DHAVE_CURL -c
Repository.lhs
Repository.lhs:1:0:
Warning: `seekRepo'
to investigate further. I've never seen problems like this
on this machine when compiling darcs.
On 4/8/06, Jason Dagit [EMAIL PROTECTED] wrote:
I just grabbed a fresh copy of the latest unstable and tried to
compile but I get these messages:
$ make
ghc -cpp -package QuickCheck -package util -package
On 4/7/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
+apply :: WriteableDirectory m
+ = [DarcsFlag]
+ - Bool -- ^ working directory - if True, this means some
inconsitencies such
+ -- as removing a non-empty directory are treated as
warnings, not
+
On 3/29/06, Eric Kow [EMAIL PROTECTED] wrote:
New submission from Eric Kow [EMAIL PROTECTED]:
(setting to bug because I need a priority, although whether this is actually a
bug is debatable)
Even though an error is given the patch is considered applied isn't?
So then to make your repo
On 3/22/06, Zachary P. Landau [EMAIL PROTECTED] wrote:
Hello,
Recently we were discussing having an archive of pending patches. I finally
managed to get patchwork[1] mostly setup. You can try it out here[2]. I
made an admin account 'test:test' if you want to try that part out. You'll
On 3/1/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
* issue79 fix, whats -l no longer computes full patch for new files
Jason,
Please remove the old version of diff_added rather than just
commenting it out. I'll be glad to apply this patch when you do.
Juliusz,
It's been so long
On 3/1/06, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
* Adds target: api-doc. api-doc is generated by haddock
This needs further discussion. Who of you would actually use
Haddock-generated docs if we decided to use Haddock markup? (I know I
wouldn't.)
I know I would, which is why I
On 2/28/06, Marnix Klooster [EMAIL PROTECTED] wrote:
Jason Dagit wrote:
On 2/28/06, Eric Kow [EMAIL PROTECTED] wrote:
New submission from Eric Kow [EMAIL PROTECTED]:
I believe this is one of the minor to-do list items we came up with in
FOSDEM.
Somebody ought to implement a 'darcs
On Feb 15, 2006, at 4:47 PM, Zooko wrote:
New submission from Zooko [EMAIL PROTECTED]:
Trying to push a large number of patches (on the order of 1500)
results in:
darcs: takeFile _darcs/patches/
20020725234351-24431-19d247bd5009053de8c6a09f10b94e2207b5f7de.gz-0
in
On Feb 3, 2006, at 6:07 PM, Zooko wrote:
New submission from Zooko [EMAIL PROTECTED]:
I've often wished for this. Also my co-worker Rob just wished for it.
Could you give an example? The idea of splitting a hunk makes no
sense to me.
Thanks,
Jason
On Jan 30, 2006, at 10:30 PM, Olivier Thauvin wrote:
This patch make darcs running a script for each patch apply by 'apply'
command.
Very nice.
If exists, _darcs/prefs/onapply is called with patch hash as first
argument. The goal is clearly to send a mail when a new commit is
done on a
My thought about this bug is that we should get rid of darcs.cgi and
adopt one of the other projects like darcsweb or darcs+trac as the
official darcs cgi. (I'm not suggesting we merge the projects)
Any thought?
Thanks,
Jason
On Jan 25, 2006, at 2:05 PM, Zooko wrote:
New submission from
On Jan 16, 2006, at 9:02 AM, Ian Lynagh wrote:
That said, it seems Jason's numbers are including mmapped files, so
it's
not clear exactly what's going on.
Yes the previous numbers did include mmap and I hadn't realized it
was important to exclude mmap'd data. Using Ian's memory
On Jan 17, 2006, at 4:17 PM, Juliusz Chroboczek wrote:
Jason, could you please repeat this test with a mere 100MB commit?
What would you like me to focus on if I do that? I've done this test
with 37MB commit
I must have missed your report of that. I'll search the archives.
I don't know
On Jan 16, 2006, at 5:34 AM, Juliusz Chroboczek wrote:
* Adds target: api-doc. api-doc is generated by haddock
Are we willing to start writing Haddock mark-up in the sources? If we
decide we do, there's no going back.
Yes, I think it would be a good thing. I also don't see it as
On Jan 16, 2006, at 6:23 AM, Juliusz Chroboczek wrote:
Jason, could you please repeat this test with a mere 100MB commit?
What would you like me to focus on if I do that? I've done this test
with 37MB commit and my findings then were pretty close to my
findings here as I recall.
On Jan 16, 2006, at 5:41 AM, Juliusz Chroboczek wrote:
Total time (wall clock)
orig: 5 hours +
no-reread: 6 minutes
Peak RES (as measured by top)
orig: 940MB
no-reread: 950MB
Am I reading this correctly? This unoptimisation makes Darcs 50 times
faster on large records while not using
On Jan 16, 2006, at 8:09 AM, Juliusz Chroboczek wrote:
Sat Jan 14 04:22:52 PST 2006 Jason Dagit [EMAIL PROTECTED]
* Do not reread freshly written patch when recording.
I've looked at the code again -- and I'm puzzled. I s'pose it's
linesPS biting us again.
Maybe, I had at least one
Zachary,
Thanks for this feature, I eagerly await it.
Thanks,
Jason
___
darcs-devel mailing list
darcs-devel@darcs.net
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
On Jan 15, 2006, at 7:34 AM, Aggelos Economopoulos wrote:
On Sunday 15 January 2006 05:04, Jason Dagit wrote:
Peak RES (as measured by top)
orig: 940MB
no-reread: 950MB
Peak VIRT (as measured by top)
orig: 1756MB
no-reread: 1289MB
When I realized that orig had consumed more time and space
On Jan 15, 2006, at 5:20 AM, Ian Lynagh wrote:
On Sat, Jan 14, 2006 at 07:04:53PM -0800, Jason Dagit wrote:
I think the numbers speak for themselves.
I think they are saying different things to me and you.
Not as different as you think. But I should have said what I was
thinking. I
On Jan 15, 2006, at 5:20 AM, Ian Lynagh wrote:
If things have regressed then the regression should be fixed, not
consolidated by forcing the patch to remain in memory.
You can find some of the discussion of the optimisation work from
before
in the archives, incidentally, e.g. around:
Hello,
I was looking a issue80 and I discovered that Repository.writePatch
reads the freshly written patch. This is a very expensive operation
given the current patch format. So I started to wonder why it does
that.
This took me to DarcsRepo.write_patch which led me to
is happy, but as I said in my email I don't know if this
change is complete. Does the return patch need to be modified at all?
Thanks,
Jason
On Jan 14, 2006, at 4:23 AM, Jason Dagit wrote:
Sat Jan 14 04:22:52 PST 2006 Jason Dagit [EMAIL PROTECTED]
* Do not reread freshly written patch
On Jan 14, 2006, at 12:22 PM, Jason Dagit wrote:
On Jan 14, 2006, at 6:13 AM, Ian Lynagh wrote:
On Sat, Jan 14, 2006 at 04:24:16AM -0800, Jason Dagit wrote:
I was looking a issue80 and I discovered that Repository.writePatch
reads the freshly written patch. This is a very expensive
On Jan 13, 2006, at 9:27 AM, Juliusz Chroboczek wrote:
* workaround for issue79
Jason,
Could you please make sure you provide more explicit patch names in
the future?
I'd be happy to. But, let me say first, this patch is superseded by
a patch named fix for issue79 which had a better
Juliusz,
This is a resend.
Thanks,
Jason
Fri Jan 13 13:24:32 PST 2006 Jason Dagit [EMAIL PROTECTED]
* removed last bits of create-repo from makefile (issue14)
New patches:
[removed last bits of create-repo from makefile (issue14)
Jason Dagit [EMAIL PROTECTED]**20060113212432] {
hunk
for testing changes? Maybe I'm being
over cautious...
Thanks,
Jason
Fri Jan 13 12:49:30 PST 2006 Jason Dagit [EMAIL PROTECTED]
* posthook success/failure messages with --verbose only
Changes behavior of posthook status messages. Use --verbose to have
posthook status messages. Error
On Jan 13, 2006, at 1:28 PM, Juliusz Chroboczek wrote:
Dear Darcs contributors,
I'm slowly starting to get the hang of that maintaining a branch
business, so I thought I'd write up how you can increase my level of
happiness. Of course, whether you actually want me to be happy is a
matter of
them as well. If this is annoying I can
separate those changes from the haddock support. They are lumped in here
because by the time I realized I had included them the patch was already
recorded.
Thanks,
Jason
Fri Jan 13 16:42:04 PST 2006 Jason Dagit [EMAIL PROTECTED]
* Adds target: api
1 - 100 of 126 matches
Mail list logo
