From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: glasser@davidglasser.net, 28637@debbugs.gnu.org
Subject: bug#28637: [PATCH] Display commit in package description, if available
Date: Tue, 24 Oct 2017 19:26:01 -0400 [thread overview]
Message-ID: <87d15ccely.fsf@users.sourceforge.net> (raw)
In-Reply-To: <833768a9ip.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Oct 2017 17:46:38 +0300")
tags 28637 fixed
close 28637 26.1
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Cc: glasser@davidglasser.net, 28637@debbugs.gnu.org
>> Date: Mon, 23 Oct 2017 19:58:32 -0400
>>
>> >From my perspective as a package maintainer, it would be very useful to
>> get the commit hash in bug reports. Getting a timestamp in place of a
>> version from MELPA users has been a pretty long-standing source of minor
>> irritation. So I would like to have this in Emacs 26 to end the
>> irritation sooner rather than later.
>>
>> Obviously it's not vital, but it usefulness vs risk ratio seems to me
>> high enough to be worth it.
>
> OK.
Pushed to emacs-26.
[1: 0c536a20fb]: 2017-10-24 19:14:30 -0400
Display commit in package description, if available (Bug#28637)
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=0c536a20fb4833bafea1c2a14b9ff2bac2a3ebd8
prev parent reply other threads:[~2017-10-24 23:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 23:06 bug#28637: [PATCH] Display commit in package description, if available David Glasser
2017-10-10 19:35 ` bug#28637: " David Glasser
2017-10-10 20:07 ` Eli Zaretskii
2017-10-10 22:05 ` David Glasser
2017-10-10 22:40 ` bug#28637: [PATCH] " Noam Postavsky
2017-10-10 22:46 ` David Glasser
2017-10-11 1:16 ` Noam Postavsky
2017-10-11 4:14 ` David Glasser
2017-10-11 10:41 ` Eli Zaretskii
2017-10-11 12:32 ` Noam Postavsky
2017-10-11 13:12 ` Eli Zaretskii
2017-10-23 23:58 ` Noam Postavsky
2017-10-24 14:46 ` Eli Zaretskii
2017-10-24 23:26 ` Noam Postavsky [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=87d15ccely.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28637@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=glasser@davidglasser.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.