From: David Bremner <david@tethera.net>
To: Robert Mast <beheerder@tekenbeetziekten.nl>
Cc: Notmuch List <notmuch@notmuchmail.org>
Subject: RE: [Spam-verdenking][english 100%] Re: another bug fix release: 0.15.2, in progress.
Date: Sun, 10 Feb 2013 09:44:51 -0400 [thread overview]
Message-ID: <87y5ew8er0.fsf@zancas.localnet> (raw)
In-Reply-To: <003b01ce0791$39239a50$ab6acef0$@nl>
Robert Mast <beheerder@tekenbeetziekten.nl> writes:
> David/Austin,
>
> I sent it as a patch to my previous patch. Is that correct, or should I first 'revert' the file to 15.1?
>
> Robert
Hi Robert;
I didn't see any followup patch from you on the list; can you tell me the
message-id?
In any case, in general you should send complete patches or or patch series
against git master, since we care both about the commit message, and what
changes are part of each commit. Most people use the git rebase command
to update patches before re-sending them.
d
prev parent reply other threads:[~2013-02-11 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:26 another bug fix release: 0.15.2, in progress david
2013-01-29 23:26 ` [PATCH 1/2] test: delay watchdog checks in emacs david
2014-01-01 15:58 ` David Bremner
2014-01-11 2:36 ` [PATCH] test/emacs: replace the use of process-attributes with kill(1) David Bremner
2014-01-11 10:14 ` Tomi Ollila
2014-01-11 17:25 ` [PATCH] test/emacs: replace the use of process-attributes with signal-process David Bremner
2014-01-11 18:50 ` Tomi Ollila
2014-01-13 0:09 ` David Bremner
2013-01-29 23:26 ` [PATCH 2/2] NEWS: News for 0.15.2 david
2013-01-30 0:37 ` another bug fix release: 0.15.2, in progress Tomi Ollila
2013-02-10 1:17 ` David Bremner
2013-02-10 13:19 ` [Spam-verdenking][english 100%] " Robert Mast
2013-02-10 13:44 ` David Bremner [this message]
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=87y5ew8er0.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=beheerder@tekenbeetziekten.nl \
--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).