# [PATCH] git clone -s documentation: force a new paragraph for the NOTE 3 messages from 2008-02-12 to 2008-02-12. Participants: Miklos Vajna, Junio C Hamano. Thread: https://gitlist.dev/t/12047 ## Miklos Vajna, 2008-02-12 00:12 Subject: [PATCH] git clone -s documentation: force a new paragraph for the NOTE Message-ID: <20080212001257.GG25954@genesis.frugalware.org> URL: https://gitlist.dev/e/20080212001257.GG25954%40genesis.frugalware.org ``` It should be loud and clear. Signed-off-by: Miklos Vajna --- I wanted this syntax when I added the NOTE but I tought it's not possible. After Junio's patch to git pull --rebase, here is a similar fix for git clone -s. Documentation/git-clone.txt | 13 +++++++------ 1 files changed, 7 insertions(+), 6 deletions(-) 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. ++ +*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. -- 1.5.4.1 ``` ## Junio C Hamano, 2008-02-12 03:07 Subject: Re: [PATCH] git clone -s documentation: force a new paragraph for the NOTE Message-ID: <7v4pce7tz8.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7v4pce7tz8.fsf%40gitster.siamese.dyndns.org In-Reply-To: <20080212001257.GG25954@genesis.frugalware.org> ``` Miklos Vajna 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. ``` ## Miklos Vajna, 2008-02-12 09:33 Subject: Re: [PATCH] git clone -s documentation: force a new paragraph for the NOTE Message-ID: <20080212093322.GJ25954@genesis.frugalware.org> URL: https://gitlist.dev/e/20080212093322.GJ25954%40genesis.frugalware.org In-Reply-To: <7v4pce7tz8.fsf@gitster.siamese.dyndns.org> ``` On Mon, Feb 11, 2008 at 07:07:39PM -0800, Junio C Hamano wrote: > The "Note" is already in bold and quite loud. I am not sure if > this is worth it. okay, i may do too much nitpicking, but i think a consistent handling of NOTEs in manpages would be nice. or this doesn't matter? :S thanks, - VMiklos ```