From: Miles Bader <miles@gnu.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/merge subtree How-To: fix typo
Date: Wed, 09 Feb 2011 18:38:59 +0900 [thread overview]
Message-ID: <buo39nxbl8s.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <20110209090821.GP27982@pengutronix.de> ("Uwe Kleine-König"'s message of "Wed, 9 Feb 2011 10:08:22 +0100")
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
>> - Please note that if the other project merges from you, then it will
>> - connects its history to yours, which can be something they don't want
>> + connect its history to yours, which can be something they don't want
> AFAIK additionally it should be "your's". Should I resend?
No, "yours" is correct.
-Miles
--
Erudition, n. Dust shaken out of a book into an empty skull.
next prev parent reply other threads:[~2011-02-09 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 9:04 [PATCH] Documentation/merge subtree How-To: fix typo Uwe Kleine-König
2011-02-09 9:08 ` Uwe Kleine-König
2011-02-09 9:38 ` Miles Bader [this message]
2011-02-09 15:58 ` Michael J Gruber
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=buo39nxbl8s.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).