From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Geoffrey Irving <irving@naml.us>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH / RFC] cherry: cache commit to patch-id pairs to avoid repeating work
Date: Sun, 8 Jun 2008 17:06:14 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806081705410.1783@racer> (raw)
In-Reply-To: <7f9d599f0806072239je3a7ec0q258d7770c15fa962@mail.gmail.com>
Hi,
On Sat, 7 Jun 2008, Geoffrey Irving wrote:
> Is starting a new thread each time I update a patch the correct way to
> do things?
I prefer a response in the existing thread, but I guess it is a matter of
personal taste (of the poster).
Ciao,
Dscho
next prev parent reply other threads:[~2008-06-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 23:36 [PATCH / RFC] cherry: cache commit to patch-id pairs to avoid repeating work Geoffrey Irving
2008-06-08 5:39 ` Geoffrey Irving
2008-06-08 16:06 ` Johannes Schindelin [this message]
2008-06-08 17:24 ` Johannes Schindelin
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=alpine.DEB.1.00.0806081705410.1783@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=irving@naml.us \
--cc=peff@peff.net \
--cc=spearce@spearce.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