{"thread":{"id":"12047","subject":"[PATCH] git clone -s documentation: force a new paragraph for the NOTE","startedAt":"2008-02-12T00:12:57Z","lastAt":"2008-02-12T09:33:22Z","messageCount":3,"participants":["Miklos Vajna","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"68466","messageId":"20080212001257.GG25954@genesis.frugalware.org","threadId":"12047","inReplyTo":null,"subject":"[PATCH] git clone -s documentation: force a new paragraph for the NOTE","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2008-02-12T00:12:57Z","receivedAt":"2008-02-12T00:12:57Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"It should be loud and clear.\n\nSigned-off-by: Miklos Vajna <vmiklos@frugalware.org>\n---\n\nI wanted this syntax when I added the NOTE but I tought it's not possible.\nAfter Junio's patch to git pull --rebase, here is a similar fix for\ngit clone -s.\n\n Documentation/git-clone.txt |   13 +++++++------\n 1 files changed, 7 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt\nindex 2341881..9758243 100644\n--- a/Documentation/git-clone.txt\n+++ b/Documentation/git-clone.txt\n@@ -62,12 +62,13 @@ OPTIONS\n \t.git/objects/info/alternates to share the objects\n \twith the source repository.  The resulting repository\n \tstarts out without any object of its own.\n-\t*NOTE*: this is a possibly dangerous operation; do *not* use\n-\tit unless you understand what it does. If you clone your\n-\trepository using this option, then delete branches in the\n-\tsource repository and then run linkgit:git-gc[1] using the\n-\t'--prune' option in the source repository, it may remove\n-\tobjects which are referenced by the cloned repository.\n++\n+*NOTE*: this is a possibly dangerous operation; do *not* use\n+it unless you understand what it does. If you clone your\n+repository using this option, then delete branches in the\n+source repository and then run linkgit:git-gc[1] using the\n+'--prune' option in the source repository, it may remove\n+objects which are referenced by the cloned repository.\n \n \n \n-- \n1.5.4.1\n"},{"id":"68480","messageId":"7v4pce7tz8.fsf@gitster.siamese.dyndns.org","threadId":"12047","inReplyTo":"20080212001257.GG25954@genesis.frugalware.org","subject":"Re: [PATCH] git clone -s documentation: force a new paragraph for the NOTE","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-02-12T03:07:39Z","receivedAt":"2008-02-12T03:07:39Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Miklos Vajna <vmiklos@frugalware.org> writes:\n\n> It should be loud and clear.\n> ...\n> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt\n> index 2341881..9758243 100644\n> --- a/Documentation/git-clone.txt\n> +++ b/Documentation/git-clone.txt\n> @@ -62,12 +62,13 @@ OPTIONS\n>  \t.git/objects/info/alternates to share the objects\n>  \twith the source repository.  The resulting repository\n>  \tstarts out without any object of its own.\n> -\t*NOTE*: this is a possibly dangerous operation; do *not* use\n> -\tit unless you understand what it does. If you clone your\n> -\trepository using this option, then delete branches in the\n> -\tsource repository and then run linkgit:git-gc[1] using the\n> -\t'--prune' option in the source repository, it may remove\n> -\tobjects which are referenced by the cloned repository.\n\nThe \"Note\" is already in bold and quite loud.  I am not sure if\nthis is worth it.\n"},{"id":"68502","messageId":"20080212093322.GJ25954@genesis.frugalware.org","threadId":"12047","inReplyTo":"7v4pce7tz8.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] git clone -s documentation: force a new paragraph for the NOTE","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2008-02-12T09:33:22Z","receivedAt":"2008-02-12T09:33:22Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Mon, Feb 11, 2008 at 07:07:39PM -0800, Junio C Hamano <gitster@pobox.com> wrote:\n> The \"Note\" is already in bold and quite loud.  I am not sure if\n> this is worth it.\n\nokay, i may do too much nitpicking, but i think a consistent handling\nof NOTEs in manpages would be nice. or this doesn't matter? :S\n\nthanks,\n- VMiklos\n"}]}