git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: "John S. Urban\"" <urbanjost@comcast.net>,
	Tor Arntsen <tor@spacetec.no>, knittl <knittl89@googlemail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] Documentation: "on for all" configuration of notes.rewriteRef
Date: Sun, 4 Sep 2011 22:28:57 +0200	[thread overview]
Message-ID: <f415402994735a60664e1f9f85be490a68b25ed3.1315167848.git.trast@student.ethz.ch> (raw)
In-Reply-To: <CABNEGjy8M-pFTOs504Q1+G_DtocJwvzDyOAsJp9cn4BOSkv1TQ@mail.gmail.com>

Users had problems finding a working setting for notes.rewriteRef.
Document how to enable rewriting for all notes.

Signed-off-by: Thomas Rast <trast@student.ethz.ch>
---
[Sorry for the spam; the first one lacks my reply blurb and the
in-reply-to. :-( ]

Tor Arntsen wrote:
> Thanks. Got it working. So it's not by default, as was suggested by
> knittl, it has to be enabled. BTW, it's not at all obvious from the
> manpage what it should be set to, there's no actual example. Found it
> by trial&error plus finding a diff for a test.

Let's document it then.  This still won't help you find out about the
option/feature in the first place, though.  Maybe we should flip the
default to enabled?

 Documentation/config.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index 0ecef9d..302b2d0 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1464,7 +1464,8 @@ notes.rewriteRef::
 	You may also specify this configuration several times.
 +
 Does not have a default value; you must configure this variable to
-enable note rewriting.
+enable note rewriting.  Set it to `refs/notes/*` to enable rewriting
+for all notes.
 +
 This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
 environment variable, which must be a colon separated list of refs or
-- 
1.7.7.rc0.420.g468b7

  parent reply	other threads:[~2011-09-04 20:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04  1:32 Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban
2011-09-04 10:02 ` PJ Weisberg
2011-09-04 13:40   ` Michael Witten
2011-09-04 14:03 ` Michael Witten
     [not found]   ` <CA+sFfMcMgPDyCi6SCS=Sc4XFrug_Ee7vbmBBkmkwfwwpXg8yCg@mail.gmail.com>
2011-09-04 14:38     ` Michael Witten
2011-09-04 17:20   ` Philip Oakley
2011-09-04 18:15     ` knittl
2011-09-04 14:30 ` knittl
2011-09-04 14:43   ` Michael Witten
2011-09-04 15:39     ` Jakub Narebski
2011-09-04 18:16   ` Tor Arntsen
2011-09-04 18:43     ` Thomas Rast
2011-09-04 19:11       ` Tor Arntsen
2011-09-04 20:18         ` John S. Urban
2011-09-04 20:28         ` Thomas Rast [this message]
2011-09-04 20:43           ` [PATCH] Documentation: "on for all" configuration of notes.rewriteRef Tor Arntsen
2011-09-07 21:23           ` Jeff King
2011-09-07 21:29             ` Thomas Rast
2011-09-07 21:35               ` Jeff King
     [not found] ` <CACx-yZ1Ce3x=ZSdm5iY3JqYjVGVs5uPnb12-tMJP7zWsGuMK_Q@mail.gmail.com>
2011-09-04 16:40   ` Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban

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=f415402994735a60664e1f9f85be490a68b25ed3.1315167848.git.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=knittl89@googlemail.com \
    --cc=tor@spacetec.no \
    --cc=urbanjost@comcast.net \
    /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).