All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2015, #05; Tue, 15)
Date: Mon, 21 Dec 2015 08:54:59 -0800	[thread overview]
Message-ID: <xmqqzix3hhcs.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1450444992-25368-1-git-send-email-szeder@ira.uka.de> ("SZEDER =?utf-8?Q?G=C3=A1bor=22's?= message of "Fri, 18 Dec 2015 14:23:12 +0100")

SZEDER Gábor <szeder@ira.uka.de> writes:

>> On the other hand, I've marked a handful of topics below as "Will
>> discard". They were all dormant after waiting for updates for quite
>> a long time; interested people may want to help resurrect them.
>
>> * sg/pretty-more-date-mode-format (2015-10-07) 1 commit
>>  - pretty: add format specifiers for short and raw date formats
>> 
>>  Introduce "%as" and "%aR" placeholders for "log --format" to show
>>  the author date in the short and raw formats.
>> 
>>  No comments after waiting for a long time.
>>  Will discard.
>
> By adding missing date format specifiers this patch improves
> consistency, improves usability of pretty format aliases, benefits at
> least one user, and does nothing wrong in its implementation.  

The above used to say:

    I have a feeling that that this is a step in a wrong direction.
    Comments?

which came from this comment of mine in $gmane/279195

>> It makes me wonder if it's time for us to move to a more extensible
>> format, e.g. "%aT(...)", in which 'T' stands for 'timestamp' and the
>> part in the parentheses can be any format string that is understood
>> by "log --date=<format>"...

to which you said this in $gmane/279236

> That would be great, especially that in [*1*].  Real words are so
> much better than one or two letter codes.

and I was hoping that at least we hear justification for not doing
the right thing and instead adding more short codes that we'd need
to maintain indefinitely, which I heard none.  Of course, it would
have been great if we saw a "more extensible format" patch ;-)

I'll keep the topic in 'pu' for now as a reminder.

      reply	other threads:[~2015-12-21 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 22:48 Junio C Hamano
2015-12-15 23:16 ` Stefan Beller
2015-12-15 23:32 ` Jeff King
2015-12-15 23:34   ` Junio C Hamano
2015-12-15 23:36   ` Junio C Hamano
2015-12-15 23:44     ` Junio C Hamano
2015-12-16  0:50       ` Jeff King
2015-12-16 15:58       ` Johannes Schindelin
2015-12-16  6:58 ` Torsten Bögershausen
2015-12-16 18:04   ` Junio C Hamano
2015-12-21 15:31     ` Torsten Bögershausen
2015-12-18 13:23 ` SZEDER Gábor
2015-12-21 16:54   ` Junio C Hamano [this message]

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=xmqqzix3hhcs.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=szeder@ira.uka.de \
    --subject='Re: What'\''s cooking in git.git (Dec 2015, #05; Tue, 15)' \
    /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

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.