From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix incorrect wording in git-merge.txt.
Date: Mon, 03 Mar 2008 09:27:29 -0800 [thread overview]
Message-ID: <7v63w3iupq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1204564483-5260-1-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Mon, 3 Mar 2008 18:14:43 +0100")
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> A merge is not necessarily with a remote branch, it can be with any
> commit object.
Thanks. Sign-off, and perhaps mention other people who helped refine the
wording in the discussion?
next prev parent reply other threads:[~2008-03-03 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 17:14 [PATCH] Fix incorrect wording in git-merge.txt Matthieu Moy
2008-03-03 17:27 ` Junio C Hamano [this message]
2008-03-03 17:52 ` Matthieu Moy
2008-03-03 18:26 ` Nicolas Pitre
2008-03-03 19:50 ` Matthieu Moy
2008-03-03 20:39 ` Nicolas Pitre
2008-03-03 21:25 ` Matthieu Moy
2008-03-03 22:10 ` Nicolas Pitre
2008-03-11 7:05 ` Andreas Ericsson
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=7v63w3iupq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--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).