2011/5/12 Jude <bookofj...@gmail.com>:
> On Thu, May 12, 2011 at 8:47 PM, RjY <r...@users.sourceforge.net> wrote:
>> In gmane.games.roguelike.crawl.devel, Johanna Ploog posted:
>>>It's in the patch guide. :)
>>>"6.) Upload the patch file(s) on Mantis at
>>>http://crawl.develz.org/mantis/main_page.php";
>>
>> Nevertheless, git is optimised for mailing list usage, as it
>> essentially codifies the process of the linux kernel mailing list.
>> git send-email and git am exist; git send-web-mantis does not.
>> It is a shame that potential code contributors are told to waste
>> five minutes fighting a web interface instead of using the tools.:)
>
> You're making the assumption here that every project functions exactly
> like LKML, or that every project would *want* to function exactly like
> LKML. ;)
>
> On a serious note, not all of our developers watch c-r-d, and Mantis
> is directly linked to IRC, where active developers can see incoming
> issues (including patches). Likewise, Mantis' interface is
> considerably nicer than SourceForge's mailling list archives
> interface.

Someone, write a script that automatically files incoming patches to
c-r-d as mantis patch items.

git send-mantis sounds good as well. ;)

But yeah, as it is in the project, patches sent to mailing list are in
danger of being buried forever unless attended to immediately, whereas
in the tracker, while they might end up rotting in there, at least
they're easily recallable, and their status is tracked (if they were
applied or not).

--Eino

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Crawl-ref-discuss mailing list
Crawl-ref-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crawl-ref-discuss

Reply via email to