From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [RFC] control, what refs are honored by core.logAllRefUpdates
Date: Tue, 12 Jul 2011 17:21:29 -0500 [thread overview]
Message-ID: <20110712222129.GA15994@elie> (raw)
In-Reply-To: <20110712182517.GA17787@sigill.intra.peff.net>
Jeff King wrote:
> I think I'd rather see something more syntactically explicit for
> resetting, though, like:
>
> [core]
> autoLogRef = heads
> autoLogRef = remotes
> autoLogRef = notes
> !autoLogRef
> autoLogref = heads
>
> (for that matter, I have often wished that "!autoLogRef" was boolean
> false, just as "autoLogRef" is boolean true). But it may not be worth
> changing the config syntax for.
Sounds worthwhile to me. I've (probably irrationally) wished before
for an abbreviation for "bare = false", too.
next prev parent reply other threads:[~2011-07-12 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 17:23 [RFC] control, what refs are honored by core.logAllRefUpdates Bert Wesarg
2011-07-12 17:57 ` Junio C Hamano
2011-07-12 18:15 ` Bert Wesarg
2011-07-12 18:25 ` Jeff King
2011-07-12 22:21 ` Jonathan Nieder [this message]
2011-07-13 8:52 ` Bert Wesarg
2011-07-13 8:59 ` Jeff King
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=20110712222129.GA15994@elie \
--to=jrnieder@gmail.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).