From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git clone -s documentation: force a new paragraph for the NOTE
Date: Mon, 11 Feb 2008 19:07:39 -0800 [thread overview]
Message-ID: <7v4pce7tz8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080212001257.GG25954@genesis.frugalware.org> (Miklos Vajna's message of "Tue, 12 Feb 2008 01:12:57 +0100")
Miklos Vajna <vmiklos@frugalware.org> writes:
> It should be loud and clear.
> ...
> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
> index 2341881..9758243 100644
> --- a/Documentation/git-clone.txt
> +++ b/Documentation/git-clone.txt
> @@ -62,12 +62,13 @@ OPTIONS
> .git/objects/info/alternates to share the objects
> with the source repository. The resulting repository
> starts out without any object of its own.
> - *NOTE*: this is a possibly dangerous operation; do *not* use
> - it unless you understand what it does. If you clone your
> - repository using this option, then delete branches in the
> - source repository and then run linkgit:git-gc[1] using the
> - '--prune' option in the source repository, it may remove
> - objects which are referenced by the cloned repository.
The "Note" is already in bold and quite loud. I am not sure if
this is worth it.
next prev parent reply other threads:[~2008-02-12 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 0:12 [PATCH] git clone -s documentation: force a new paragraph for the NOTE Miklos Vajna
2008-02-12 3:07 ` Junio C Hamano [this message]
2008-02-12 9:33 ` Miklos Vajna
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=7v4pce7tz8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).