From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's not in git.git
Date: Sat, 17 Nov 2007 18:27:09 -0500 [thread overview]
Message-ID: <20071117232709.GA19186@fieldses.org> (raw)
In-Reply-To: <7vlk8wshii.fsf@gitster.siamese.dyndns.org>
On Sat, Nov 17, 2007 at 01:12:53PM -0800, Junio C Hamano wrote:
> * "Why a merge is more difficult to bisect" document.
>
> I think the last text with rewording suggestion on the list
> was good. Should I take that directly, or pull through
> Bruce?
I can take a look tonight or tommorow (Sunday) morning. I'll also skim
back through my inbox for other user-manual and related patches (I know
I've been neglecting it for a while...), but if people know of anything
that's been overlooked they could resend.
--b.
prev parent reply other threads:[~2007-11-17 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 21:12 What's not in git.git Junio C Hamano
2007-11-17 23:27 ` 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=20071117232709.GA19186@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).