All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Adeodato Simó" <dato@net.com.org.es>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v2] log: make --abbrev-commit's ellipsis configurable
Date: Fri, 13 Feb 2009 16:32:26 +0100	[thread overview]
Message-ID: <4995928A.5000908@viscovery.net> (raw)
In-Reply-To: <1234535092-20133-1-git-send-email-trast@student.ethz.ch>

Thomas Rast schrieb:
> So we introduce a new variable format.abbrevEllipsis that defaults to
> true (previous behaviour).

How about format.hideAbbrevDots that defaults to false? Then you can write
in the config file:

    [format]
         hideAbbrevDots

(note: without '= true').

Even though I usually detest double negations (and I would count
hideAbbrevDots=false as one), the ability to set the non-default value of
a Boolean variable in this way trumps my taste.

-- Hannes

  reply	other threads:[~2009-02-13 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 12:58 [PATCH] log: make --abbrev-commit's ellipsis configurable Thomas Rast
2009-02-13 13:20 ` Johannes Schindelin
2009-02-13 13:37   ` Thomas Rast
2009-02-13 13:47     ` Johannes Schindelin
2009-02-13 14:24       ` [PATCH v2] " Thomas Rast
2009-02-13 15:32         ` Johannes Sixt [this message]
     [not found]           ` <m363jeux00.fsf@localhost.localdomain>
2009-02-13 16:45             ` Jakub Narebski
2009-02-13 19:27     ` [PATCH] " Jeff King
2009-02-13 21:32 ` Junio C Hamano
2009-02-13 22:10   ` [PATCH] log: do not print ellipses with --abbrev-commit Thomas Rast
2009-02-13 22:24     ` 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=4995928A.5000908@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=dato@net.com.org.es \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=trast@student.ethz.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.