From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Frank Lichtenheld <frank@lichtenheld.de>, git@vger.kernel.org
Subject: Re: [PATCH] user-manual: fix branch names in examples
Date: Mon, 14 May 2007 17:38:37 -0400 [thread overview]
Message-ID: <20070514213837.GE23090@fieldses.org> (raw)
In-Reply-To: <7viravm6s7.fsf@assigned-by-dhcp.cox.net>
On Mon, May 14, 2007 at 02:31:20PM -0700, Junio C Hamano wrote:
> Thanks everybody for participating in these fixups.
>
> Bruce, how heavy is your workload these days?
Probably lighter than yours.
> Would you mind if I ask you to collect the list comments, have me wait
> for a few days until the discussions and updates settle down and give
> me "Ok, all ready to be pulled" after that?
Yep, that should be no problem.
--b.
prev parent reply other threads:[~2007-05-14 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:51 [PATCH 08/10] user-manual: add a "counting commits" example Frank Lichtenheld
2007-05-14 16:03 ` J. Bruce Fields
2007-05-14 16:05 ` [PATCH] user-manual: fix branch names in examples J. Bruce Fields
2007-05-14 21:31 ` Junio C Hamano
2007-05-14 21:38 ` J. Bruce Fields [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=20070514213837.GE23090@fieldses.org \
--to=bfields@fieldses.org \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).