git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc: add note about ignoring --no-create-reflog

From
Jeff King <peff@peff.net>
Date
Feb 1, 2017, 23:19 UTC
Message-ID
<20170201231939.hxhhujpzyb2cqq7a@sigill.intra.peff.net>
In-Reply-To
<xmqqmve5mrpe.fsf@gitster.mtv.corp.google.com>
On Wed, Feb 01, 2017 at 03:11:57PM -0800, Junio C Hamano wrote:
Show 11 quoted lines
> diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
> index 5516a47b54..102e426fd8 100644
> --- a/Documentation/git-branch.txt
> +++ b/Documentation/git-branch.txt
> @@ -91,6 +91,9 @@ OPTIONS
>  	based sha1 expressions such as "<branchname>@\{yesterday}".
>  	Note that in non-bare repositories, reflogs are usually
>  	enabled by default by the `core.logallrefupdates` config option.
> +	The negated form `--no-create-reflog` does not override the
> +	default, even though it overrides `--create-reflog` that appears
> +	earlier on the command line.

Should this perhaps say "currently" or "this may change in the future", so that people (including those who might want to fix it later) know that it's a limitation and not intentional?

I'd also probably say it a little shorter, like:
  The negated form `--no-create-reflog` only overrides an earlier
  `--create-reflog`, but currently does not negate the setting of
  `core.logallrefupdates`.

I guess that really isn't much shorter (I wondered if you could cut out the "overrides --create-reflog" part, since that is the normal and expected behavior, but I had trouble wording it to do so).

-Peff
Previous: Cornelius WeigNext: Cornelius Weig
Message 6 of 10 in “doc: add note about ignoring --no-create-reflog”
  1. doc: add note about ignoring --no-create-reflogcornelius.weig@tngtech.com, Feb 1, 2017
  2. Junio C HamanoFeb 1, 2017
  3. Jeff KingFeb 1, 2017
  4. Junio C HamanoFeb 1, 2017
  5. Cornelius WeigFeb 1, 2017
  6. Jeff KingFeb 1, 2017
  7. Cornelius WeigFeb 1, 2017
  8. Junio C HamanoFeb 1, 2017
  9. Jeff KingFeb 1, 2017
  10. Junio C HamanoFeb 1, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.