From: Karl Wiberg <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH 1/2] Rename the mail --refid and --noreply options to match Git
Date: Fri, 8 Jan 2010 07:35:06 +0100 [thread overview]
Message-ID: <b8197bcb1001072235ga32ffb7r4ede6eeec1944141@mail.gmail.com> (raw)
In-Reply-To: <20100107160932.3226.95737.stgit@pc1117.cambridge.arm.com>
Looks good.
--
Karl Wiberg, kha@treskal.com
subrabbit.wordpress.com
www.treskal.com/kalle
prev parent reply other threads:[~2010-01-08 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 16:09 [StGit PATCH 1/2] Rename the mail --refid and --noreply options to match Git Catalin Marinas
2010-01-07 16:09 ` [StGit PATCH 2/2] Pass the --in-reply-to and --no-thread options to git send-email Catalin Marinas
2010-01-08 6:43 ` Karl Wiberg
2010-01-08 12:33 ` Catalin Marinas
2010-01-08 6:35 ` Karl Wiberg [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8197bcb1001072235ga32ffb7r4ede6eeec1944141@mail.gmail.com \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).