From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 4BAD6429E34 for ; Mon, 30 Jan 2012 15:39:03 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsJCnudFc5mh for ; Mon, 30 Jan 2012 15:39:02 -0800 (PST) Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by olra.theworths.org (Postfix) with ESMTP id C1C08431FBC for ; Mon, 30 Jan 2012 15:39:02 -0800 (PST) X-AuditID: 12074424-b7fae6d000000906-6e-4f272a16151c Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 4B.7F.02310.61A272F4; Mon, 30 Jan 2012 18:39:02 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q0UNd2d6007900 for ; Mon, 30 Jan 2012 18:39:02 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0UNd1Od005813 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 30 Jan 2012 18:39:01 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1Rs0na-0002U9-6I for notmuch@notmuchmail.org; Mon, 30 Jan 2012 18:38:10 -0500 Date: Mon, 30 Jan 2012 18:38:10 -0500 From: Austin Clements To: notmuch@notmuchmail.org Subject: Re: [PATCH] lib: update notmuch_tags_get example to reflect api change Message-ID: <20120130233810.GT17991@mit.edu> References: <1327955744-13031-1-git-send-email-allan_wind@lifeintegrity.com> <87aa54x16u.fsf@awakening.csail.mit.edu> <20120130230519.GB18672@lifeintegrity.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120130230519.GB18672@lifeintegrity.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsUixG6nriumpe5v8PKRkMX1mzOZHRg9nq26 xRzAGMVlk5Kak1mWWqRvl8CVsWTFUaaCL5wVv04fYGpgfMfexcjJISFgIrF89QpGCFtM4sK9 9WxdjFwcQgL7GCXuHz3LCuGcY5S4+H49O4TznEni7voeFgjnEKPExqZlYLNYBFQl9j08wAZi swloSGzbvxxsroiAtMTOu7NZQWxhgUCJsw/mA8U5OHgFdCR69zlCzFnCKHFr61RmkBpeAUGJ kzOfsIDYzAJaEjf+vWQCqWcGmrP8HwdImFPAXGLD9EVg5aICKhJTTm5jm8AoOAtJ9ywk3bMQ uhcwMq9ilE3JrdLNTczMKU5N1i1OTszLSy3SNdfLzSzRS00p3cQIDlYXlR2MzYeUDjEKcDAq 8fAKfVLzF2JNLCuuzD3EKMnBpCTKe0Rd3V+ILyk/pTIjsTgjvqg0J7UYGB4czEoivG9WA5Xz piRWVqUW5cOkpDlYlMR5NbTe+QkJpCeWpGanphakFsFkZTg4lCR4szWBhgoWpaanVqRl5pQg pJk4OEGG8wANbwGp4S0uSMwtzkyHyJ9iVJQS5+0ASQiAJDJK8+B6YcnkFaM40CvCvDNAqniA iQiu+xXQYCagwc8ZVEEGlyQipKQaGMOmLGxKMLJM4Xiq9ynObp9uoHLAyf8JC6pOlfz7yz01 5mEtw0ZLnx41rbgDLf9/fFlxlulLiq2Qdu+iY08Z8q6fLxLriWAJF5i7g91BQKylTE/qwL3i YrnZium7g3qWvNorr86nlpuT9TF+1k2f3JVJy2UXcO5qlb7p/cRWa5ZBp/zclML5SizFGYmG WsxFxYkAkosLPQEDAAA= X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 23:39:03 -0000 Quoth Allan Wind on Jan 30 at 6:05 pm: > On 2012-01-30 17:42:01, Austin Clements wrote: > > Sorry, I replied to the wrong one. This one LGTM. > > > > (BTW, for future reference, it's helpful if you send later versions in > > reply to the first version so that they're grouped in threads. Sorry > > that the documentation on notmuch's coding conventions is so scattered > > and lacking. We're working on it.) > > Will do. I deleted the first message by mistake, and did not see > Message-Ids in the archives. Does git send-email hang on to the > message-ids for replies? That would be nice, but no. I think you're right that neither the Mailman archive nor Nabble give access to message IDs. The mbox archive does, of course, though that requires downloading and hunting through the entire list history (though I know of an MUA that's really good at that sort of thing). Another thing you can do to encourage reviewing of multi-version patches is to add a version number to the subject. It makes it easier for reviewers to recognize what they have or haven't looked at. git send-email makes this easy, though non-obvious: --subject-prefix='PATCH v2' will indicate that a patch (or series) is version 2 in the conventional way.