unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Basil Contovounesios <contovob@tcd.ie>
Cc: "Alan Mackenzie" <acm@muc.de>,
	"Mattias Engdegård" <mattias.engdegard@gmail.com>,
	"Paul Eggert" <eggert@cs.ucla.edu>,
	64069@debbugs.gnu.org
Subject: bug#64069: 30.0.50; Mistyped shy group regexps
Date: Thu, 15 Jun 2023 15:14:38 +0300	[thread overview]
Message-ID: <83e99e89-cc0a-ee90-66b9-8354975a04c7@gutov.dev> (raw)
In-Reply-To: <87zg5141j7.fsf@epfl.ch>

On 15/06/2023 10:39, Basil Contovounesios wrote:
>> IIUC, the change in commit 576fba5f58d removed the complex dates from the output
>> (which we parse), replacing them with the simple yyyy-mm-dd format (that's what
>> --date=short does). Seems like I tried (8 years ago) to retain the compatibility
>> with the previous output in case we'll make the format configurable someday, but
>> that still hasn't happened.
> Is it not configurable via vc-git-annotate-switches?
> When invoking git with multiple --date= options, the last one wins.

All right. I'm not sure if people took advantage of this capability, but 
if you want to keep supporting it, that is fine by me, too.

Thanks.





  reply	other threads:[~2023-06-15 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 16:43 bug#64069: 30.0.50; Mistyped shy group regexps Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-15  1:45 ` Dmitry Gutov
2023-06-15  7:39   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-15 12:14     ` Dmitry Gutov [this message]
2023-06-15 20:58 ` Alan Mackenzie
2023-06-17 13:26   ` Alan Mackenzie
2023-06-17 15:39     ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83e99e89-cc0a-ee90-66b9-8354975a04c7@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=64069@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=contovob@tcd.ie \
    --cc=eggert@cs.ucla.edu \
    --cc=mattias.engdegard@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).