1 patch for repository http://darcs.net:
Mon Mar 12 19:25:06 EDT 2012 Will Langstroth <will@langstroth.com>
* Remove the function delimiters
find . -name '*.hs' | xargs -n 2 -I {} sed -i -e '/^------------------------------------------------------------------------------/d' {}
Easiest negative commit ever. When my other patches get commited, I'll do that again, and the repo will once again be function delimiter free.
This patch now conflicts with the screened repository, could you send it
again?
Also, how do you make sure you don't delete lines that were in the code
before your patch? Or do we always want to remove them?
I can do it again, pretty easily (see the comment on the commit). There
aren't that many examples of "dashed lines" in the code, and only the files
I altered have ones longer than 70 dashes long. I guess "grep" is the short
answer.
On 16 March 2012 19:16, Guillaume Hoffmann <bugs@darcs.net> wrote:
>
> Guillaume Hoffmann <guillaumh@gmail.com> added the comment:
>
> This patch now conflicts with the screened repository, could you send it
> again?
>
> Also, how do you make sure you don't delete lines that were in the code
> before your patch? Or do we always want to remove them?
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/patch753>
> __________________________________
>
Sigh. Here I thought I was doing it the right way. Roger; wilco.
On 19 March 2012 11:34, Guillaume Hoffmann <bugs@darcs.net> wrote:
>
> Guillaume Hoffmann <guillaumh@gmail.com> added the comment:
>
> Try again without putting the patch number into the patch name :-)
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/patch753>
> __________________________________
>
Thanks Will. I'm screening this right away to prevent conflicts.
1 patch for repository http://darcs.net:
Thu Mar 22 15:00:12 ART 2012 Guillaume Hoffmann <guillaumh@gmail.com>
* Remove the function delimiters
Initial patch by Will Langstroth.