[notmuch] patchwork test instance

also sprach Carl Worth [2010.02.24.2008 +0100]: > I agree that in its current form it's not useful, (it seems to be just a > long list of the patches that have ever been submitted). > > I seem to recall Martin saying that patches that get accepted will be > automatically detected and removed

[notmuch] patchwork test instance

also sprach Carl Worth [2010.02.24.2010 +0100]: > > Carl, would you consider bouncing messages to addresses like > > patchwork+rejected at patchwork.notmuchmail.org? That would make it > > trivial for me to write glue to update patchwork automatically. > > Now you're talking my language, Martin!

[notmuch] patchwork test instance

On Thu, 11 Feb 2010 11:22:16 +1300, martin f krafft wrote: > Carl, would you consider bouncing messages to addresses like > patchwork+rejected at patchwork.notmuchmail.org? That would make it > trivial for me to write glue to update patchwork automatically. Now you're talking my language,

[notmuch] patchwork test instance

On Wed, 10 Feb 2010 10:25:49 +0100, "Sebastian Spaeth" wrote: > On Wed, 10 Feb 2010 16:25:03 +1300, martin f krafft > wrote: > > > http://patchwork.madduck.net/project/notmuch/list/ now exists. And even as http://patchwork.notmuchmail.org now. > As long as patches aren't being marked as

Re: [notmuch] patchwork test instance

also sprach Carl Worth cwo...@cworth.org [2010.02.24.2010 +0100]: Carl, would you consider bouncing messages to addresses like patchwork+rejec...@patchwork.notmuchmail.org? That would make it trivial for me to write glue to update patchwork automatically. Now you're talking my language,

[notmuch] patchwork test instance

also sprach Sebastian Spaeth [2010.02.10.2225 +1300]: > "notmuch dump tag:notmuch and tag:patch" could be used to construct a > list of "accepted", "willnottakeit","superseded" and "pending" lists or > whatever. If that list were made accessible somewhere, this would be > super useful. At least

[notmuch] patchwork test instance

also sprach David Bremner [2010.02.10.2149 +1300]: > I'm not sure what merging patches means here; some kind of squash > operation? Anyway it seemed to me that every every patch series > that I looked at was broken into individual patches. Maybe I am > just unlucky, or does patchwork really not

[notmuch] patchwork test instance

also sprach martin f krafft [2010.02.02.1131 +1300]: > I investigated some patch/issue trackers over the weekend. Here's my > summary/reply. > > The executive summary is that > http://patchwork.madduck.net/project/notmuch/list/ now exists. > I have not really used it for anything real, so if

[notmuch] patchwork test instance

On Wed, 10 Feb 2010 16:25:03 +1300, martin f krafft wrote: > > http://patchwork.madduck.net/project/notmuch/list/ now exists. > > Are people actually using it? I know that merging patches is > impossible, and that sucks, but otherwise: is this something to keep > around, or should I take the

[notmuch] patchwork test instance

On Wed, 10 Feb 2010 16:25:03 +1300, martin f krafft wrote: > > Are people actually using it? I know that merging patches is > impossible, and that sucks, but otherwise: is this something to keep > around, or should I take the site offline again? I'm not sure what merging patches means here;

Re: [notmuch] patchwork test instance

On Wed, 10 Feb 2010 16:25:03 +1300, martin f krafft madd...@madduck.net wrote: Are people actually using it? I know that merging patches is impossible, and that sucks, but otherwise: is this something to keep around, or should I take the site offline again? I'm not sure what merging patches

Re: [notmuch] patchwork test instance

On Wed, 10 Feb 2010 16:25:03 +1300, martin f krafft madd...@madduck.net wrote: http://patchwork.madduck.net/project/notmuch/list/ now exists. Are people actually using it? I know that merging patches is impossible, and that sucks, but otherwise: is this something to keep around, or should I

Re: [notmuch] patchwork test instance

also sprach David Bremner brem...@unb.ca [2010.02.10.2149 +1300]: I'm not sure what merging patches means here; some kind of squash operation? Anyway it seemed to me that every every patch series that I looked at was broken into individual patches. Maybe I am just unlucky, or does patchwork

Re: [notmuch] patchwork test instance

also sprach martin f krafft madd...@madduck.net [2010.02.02.1131 +1300]: I investigated some patch/issue trackers over the weekend. Here's my summary/reply. The executive summary is that http://patchwork.madduck.net/project/notmuch/list/ now exists. I have not really used it for anything

[notmuch] patchwork test instance (was: Git feature branch)

On Tue, 2 Feb 2010 11:31:12 +1300, martin f krafft wrote: > Arguably, being patch-centric means that a project has a higher > barrier of entry, but it also means that if someone wants something, > they know that they'll have to somehow end up with a patch. The way > this happens on Git is that

[notmuch] patchwork test instance (was: Git feature branch)

I investigated some patch/issue trackers over the weekend. Here's my summary/reply. The executive summary is that http://patchwork.madduck.net/project/notmuch/list/ now exists. I have not really used it for anything real, so if some of you feel inclined to give it a shot, sign up and triage away!

[notmuch] patchwork test instance (was: Git feature branch)

I investigated some patch/issue trackers over the weekend. Here's my summary/reply. The executive summary is that http://patchwork.madduck.net/project/notmuch/list/ now exists. I have not really used it for anything real, so if some of you feel inclined to give it a shot, sign up and triage away!