Hi John, On Tue, Dec 23, 2008 at 17:59:02 -0800, John Meacham wrote: > I don't know if many people played with my 'HTTP' submission feature for > darcs, but one of the interesting things I did with it was to have the > submission script actually perform some basic lint such as checking for > trailing whitespace before accepting the patch. (my server side > submission script, not darcs itself)
We've tried to use it for darcs.net, for what it's worth, but were stymied by some silly mail issues (I think it was the machine that hosts darcs.net is not the same as the mail server and when it tries to send mail to a darcs.net address, it tries to do a local delivery... we never got around to dealing with that, and will probably just mail to my gmail address directly). It's one thing that sits on our TODO list and resurfaces from time to time :-/ > On that subject, when I originally implemented the REST (I think is the > buzzword) patch submission feature, there were a few competing http > implementations so I only did it for the native haskell version as an > initial case. What is the state of things nowadays? I'd like to bring > the patch up to the state of the art. We still support all three of HTTP, libcurl and libwww. Now that HTTP apparantly has some really nice performance improvements, we can maybe consider consolidating on that, or maybe making it the default. But there's always the concern about maturity. I do wonder if libwww support is important and if we should think about paring down... -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpvp4Hv7FTOv.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
