From: Thomas Schwinge <thomas@schwinge.name>
To: Austin Clements <amdragon@mit.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] notmuch restore --accumulate
Date: Fri, 09 Sep 2011 19:22:49 +0200 [thread overview]
Message-ID: <87fwk53a1i.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <CAH-f9WutmDs2=UELduO66YPPFhy1g8D4_xNhnEjOiWaJMv7m5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
Hi!
On Fri, 9 Sep 2011 12:13:06 -0400, Austin Clements <amdragon@mit.edu> wrote:
> The idea behind sending the test first is that people can see that it fails
> and that the subsequent patch indeed fixes it. What I find works well is to
> submit the test case with the test marked as broken and then the main patch,
> including the change to un-mark it as broken.
Ah, that's indeed a good approach for bug fixes (and it also preserves
git bisect compatibility), but still: why separate patches for new
functionality? (I'm not trying to be a pain here, but would like to
understand your rationale behind this.)
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2011-09-09 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:07 [PATCH] notmuch restore --accumulate Thomas Schwinge
2011-09-05 19:31 ` Jameson Graef Rollins
2011-09-09 9:06 ` Louis Rilling
2011-09-09 9:45 ` Thomas Schwinge
2011-09-09 16:13 ` Austin Clements
2011-09-09 17:22 ` Thomas Schwinge [this message]
2011-09-09 17:35 ` Austin Clements
2011-09-09 18:58 ` Jameson Graef Rollins
2011-09-29 18:24 ` [PATCH] patchformatting: Test Suite Enhancements Thomas Schwinge
2011-09-29 17:36 ` [PATCH, v2] notmuch restore --accumulate Thomas Schwinge
2011-09-29 17:37 ` Thomas Schwinge
2011-10-21 19:47 ` Updated v3 patches for " David Bremner
2011-10-21 19:47 ` [PATCH 1/6] test/test-lib.sh: update comments David Bremner
2011-10-21 19:47 ` [PATCH 2/6] test/dump-restore: expand test suite for dump-restore, make more robust David Bremner
2011-10-21 19:47 ` [PATCH 3/6] test/dump-restore: add tests for restore --accumulate David Bremner
2011-10-21 19:47 ` [PATCH 4/6] notmuch-restore: implement --accumulate option David Bremner
2011-10-21 19:47 ` [PATCH 5/6] test/dump-restore: Fix quoting on grep David Bremner
2011-10-21 19:47 ` [PATCH 6/6] notmuch-restore: check for extra arguments David Bremner
2011-10-21 22:21 ` [PATCH 1/2] notmuch.1: typo fixes new wording for dump/restore David Bremner
2011-10-21 22:21 ` [PATCH 2/2] docs: Update news, man page, and online help for restore --accumulate David Bremner
2011-10-23 19:50 ` Updated v3 patches for notmuch " David Bremner
2011-10-16 21:48 ` [PATCH, v2] " David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwk53a1i.fsf@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=amdragon@mit.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).