--- /dev/null
+Return-Path: <madduck@lapse.rw.madduck.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 4DFE9431FBF\r
+ for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 14:32:11 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.483\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.483 tagged_above=-999 required=5 tests=[AWL=2.116,\r
+ BAYES_00=-2.599] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id RbbCzSMPYlpD for <notmuch@notmuchmail.org>;\r
+ Mon, 1 Feb 2010 14:32:09 -0800 (PST)\r
+Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96])\r
+ by olra.theworths.org (Postfix) with ESMTP id E07C4431FBD\r
+ for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 14:32:08 -0800 (PST)\r
+Received: from lapse.rw.madduck.net (lapse.nz.madduck.net\r
+ [IPv6:2001:4428:234::1])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (Client CN "lapse.rw.madduck.net",\r
+ Issuer "CAcert Class 3 Root" (verified OK))\r
+ by clegg.madduck.net (postfix) with ESMTPS id AA1101D409D\r
+ for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 23:32:03 +0100 (CET)\r
+Received: by lapse.rw.madduck.net (Postfix, from userid 1000)\r
+ id B471EFF; Tue, 2 Feb 2010 11:31:12 +1300 (NZDT)\r
+Date: Tue, 2 Feb 2010 11:31:12 +1300\r
+From: martin f krafft <madduck@madduck.net>\r
+To: notmuch@notmuchmail.org\r
+Message-ID: <20100201223112.GA20288@lapse.rw.madduck.net>\r
+Mail-Followup-To: notmuch@notmuchmail.org\r
+References: <87my083mgh.fsf@SSpaeth.de> <87d4148s2c.fsf@lillypad.riseup.net>\r
+ <4B595D3A.1030901@SSpaeth.de> <87636u34lw.fsf@SSpaeth.de>\r
+ <87d411zvz8.fsf@yoom.home.cworth.org>\r
+ <20100125213231.GB15987@lapse.rw.madduck.net>\r
+ <960df8f6a8a08f2ca3aceef5a216d691.squirrel@webmail.sspaeth.de>\r
+ <87wrz4fqsw.fsf@lillypad.riseup.net>\r
+ <20100127194149.GA23034@lapse.rw.madduck.net>\r
+ <20100128070522.GA18649@ukfsn.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; micalg=pgp-ripemd160;\r
+ protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X"\r
+Content-Disposition: inline\r
+In-Reply-To: <20100128070522.GA18649@ukfsn.org>\r
+X-Motto: Keep the good times rollin'\r
+X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686\r
+X-Spamtrap: madduck.bogus@madduck.net\r
+X-Subliminal-Message: debian/rules!\r
+User-Agent: Mutt/1.5.20 (2009-06-14)\r
+X-Virus-Scanned: clamav-milter 0.95.3 at clegg\r
+X-Virus-Status: Clean\r
+Subject: [notmuch] patchwork test instance (was: Git feature branch)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 01 Feb 2010 22:32:11 -0000\r
+\r
+\r
+--LZvS9be/3tNcYl/X\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+I investigated some patch/issue trackers over the weekend. Here's my\r
+summary/reply.\r
+\r
+The executive summary is that\r
+http://patchwork.madduck.net/project/notmuch/list/ now exists.\r
+I have not really used it for anything real, so if some of you feel\r
+inclined to give it a shot, sign up and triage away! Feedback\r
+welcome.\r
+\r
+also sprach James Rowe <jnrowe@gmail.com> [2010.01.28.2005 +1300]:\r
+> Roundup has command line and email interfaces. The email interface is\r
+> quite similar to debian's. I've never used a launchpad hosted project\r
+> so I can't compare it.\r
+\r
+Roundup is an issue tracker, while Patchwork is a patch tracker.\r
+They are fundamentally distinct, but there are overlaps. What led me\r
+to go the Patchwork-path is that projects like the kernel and Git\r
+don't use issue trackers but work entirely patch-based.\r
+\r
+I don't know if that is the right way to do things, but having an\r
+issue tracker that fills up with bugs and wishlist items lacking\r
+patches is no better in the long run than not having an issue\r
+tracker.\r
+\r
+Arguably, being patch-centric means that a project has a higher\r
+barrier of entry, but it also means that if someone wants something,\r
+they know that they'll have to somehow end up with a patch. The way\r
+this happens on Git is that you either write it yourself and bring\r
+it up to discussion (which is what patchwork facilitates), or\r
+constructively theorise the functionality until someone else\r
+submits a patch.\r
+\r
+> Google's codereview tool has a nice interface for collecting and\r
+> commenting on patches, but I suspect that suggestion will also meet with\r
+> a degree of friction. To me codereview feels like patchwork with\r
+> polish.\r
+\r
+Maybe you could take some ideas from codereview and inform the\r
+patchwork people about them?\r
+\r
+> Both gitorious and github have commenting functionality built in.\r
+> Commenting on commits in a fork is as easy as opening the commit in\r
+> a browser. I use something along the lines of the following script to\r
+> open commits on github:\r
+>=20\r
+> #! /bin/sh\r
+> BASE=3D$(git config remote.${2:-origin}.url | sed 's,git\(@\|://\)\([=\r
+^:/]*\)[:/]\(.*\).git,http://\2/\3/commit,')\r
+> COMMIT=3D$(git rev-parse ${1:-HEAD})\r
+> sensible-browser ${BASE}/${COMMIT}\r
+>=20\r
+> Using github or gitorious you can easily find and track forks from one\r
+> place as well, which makes discovering new work much easier. Github\r
+> even provides a pretty single page interface to the work going on in\r
+> other forks, gitorious requires a little more leg work to do the same\r
+> but not much.\r
+\r
+Git now has commit notes, but it doesn't seem like that's integrated\r
+with Github/Gitorious.\r
+\r
+Mind you, patchwork isn't integrated at all with Git. It should be\r
+possible to set it up to automatically flag patches that are\r
+accepted into mainline, next, or pu.\r
+\r
+The benefit of patchwork is that discussion isn't moved to the web,\r
+but patchwork hooks into the mailing list, so discussion can stay\r
+where it should IMHO be.\r
+\r
+> For a couple of hosted projects we use at the office we email the\r
+> individual entries from http://github.com/$user/$project/comments.atom\r
+> to the mailing list so they're /forcibly/ seen by everybody :)\r
+\r
+Right, but replying requires them to open a browser and be online at\r
+the time, right?\r
+\r
+\r
+\r
+Anyway, I suggest we give patchwork a try. It occurs to me that\r
+notmuch can pretty much do all of what patchwork is doing =E2=80=94 after\r
+all, it's just tagging patches/threads, but until we have\r
+synchronisable tags and a mailing list archive based on notmuch\r
+(which could then replace patchwork), I think we'll need to employ\r
+a third tool.\r
+\r
+--=20\r
+martin | http://madduck.net/ | http://two.sentenc.es/\r
+=20\r
+"what's your conceptual continuity? --\r
+ well, it should be easy to see:\r
+ the crux of the bisquit is the apopstrophe!"\r
+ -- frank zappa\r
+=20\r
+spamtraps: madduck.bogus@madduck.net\r
+\r
+--LZvS9be/3tNcYl/X\r
+Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"\r
+Content-Description: Digital signature (see http://martin-krafft.net/gpg/)\r
+Content-Disposition: inline\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iEYEAREDAAYFAktnVi0ACgkQIgvIgzMMSnVpmQCeNAE//qcT8J5I7s7f/3BbLFxB\r
+3TIAn2Ha7h9pacquF0AmIljRHclIgiIo\r
+=qd+m\r
+-----END PGP SIGNATURE-----\r
+\r
+--LZvS9be/3tNcYl/X--\r
projects / notmuch-archives.git / commitdiff