unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Rohan Hart <rohan.hart@fronde.com>
Cc: 27453@debbugs.gnu.org
Subject: bug#27453: 25.1; vc/log-view.el log-view-message-re doesn't support newer Darcs log format
Date: Sun, 21 Jul 2019 19:40:25 +0200	[thread overview]
Message-ID: <877e8b477a.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CAKQntwKb-bifSUzc6VsVtkqHdLO+xD67Br93an__JUmT6X6UMw@mail.gmail.com> (Rohan Hart's message of "Fri, 23 Jun 2017 00:49:33 +0000")

Rohan Hart <rohan.hart@fronde.com> writes:

> Darcs now shows the internal hash for each patch in a format like:
>
> patch f4128969c4700a0b34414390d04159cb6b11b4e5
> Author: bob <bob>
> Date:   Sun May 21 22:44:55 NZST 2017
>   * patch name
>   - further details
>
> Adding the regex "\\|^patch \\(?1:[.0-9a-f]+\\)" to log-view-message-re
> seems to be sufficient to use the hash.

Hm...  Unless I'm mistaken, Emacs doesn't support Darcs?  I ran

$ darcs clone https://hub.darcs.net/onetom/0wnDB

and Emacs then claimed that the files in that directory weren't under
source control?  So I'm unsure how this would help...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-07-21 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  0:49 bug#27453: 25.1; vc/log-view.el log-view-message-re doesn't support newer Darcs log format Rohan Hart
2019-07-21 17:40 ` Lars Ingebrigtsen [this message]
2019-07-21 20:36   ` Rohan Hart
2019-07-22 12:28     ` Lars Ingebrigtsen
2019-07-22 20:42       ` Rohan Hart
2019-07-23 11:31         ` Lars Ingebrigtsen
2019-07-23 20:57           ` Rohan Hart
2019-07-24 12:32             ` Lars Ingebrigtsen
2020-08-20 16:01               ` Lars Ingebrigtsen

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=877e8b477a.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=27453@debbugs.gnu.org \
    --cc=rohan.hart@fronde.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).