From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] docs: say "commits" in the --depth option wording for git-clone
Date: Wed, 13 Jan 2016 19:22:31 +0100 [thread overview]
Message-ID: <569695E7.4020704@gmail.com> (raw)
In-Reply-To: <568F7EDD.9020003@gmail.com>
On 08.01.2016 10:18, Sebastian Schuberth wrote:
> It is not wrong to talk about "revisions" here, but in this context
> revisions are always commits, and that is how we already name it in the
> git-fetch docs. So align the docs by always referring to "commits".
Sorry for the missing sign-off, feel free to amend that in pu:
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
--
Sebastian Schuberth
next prev parent reply other threads:[~2016-01-13 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 12:30 Questions on passing --depth to git-clone vs. git-fetch Sebastian Schuberth
2016-01-06 12:41 ` Duy Nguyen
2016-01-06 13:04 ` Sebastian Schuberth
2016-01-06 13:06 ` [PATCH] docs: clarify that passing --depth to git-clone implies --single-branch Sebastian Schuberth
2016-01-07 19:45 ` Junio C Hamano
2016-01-08 9:18 ` [PATCH] docs: say "commits" in the --depth option wording for git-clone Sebastian Schuberth
2016-01-13 18:22 ` Sebastian Schuberth [this message]
2016-01-08 9:32 ` [PATCH] docs: clarify that --depth for git-fetch works with newly initialized repos Sebastian Schuberth
2016-01-13 18:24 ` Sebastian Schuberth
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=569695E7.4020704@gmail.com \
--to=sschuberth@gmail.com \
--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).