* bug#28637: [PATCH] Display commit in package description, if available
@ 2017-09-28 23:06 David Glasser
2017-10-10 19:35 ` bug#28637: " David Glasser
2017-10-10 22:40 ` bug#28637: [PATCH] " Noam Postavsky
0 siblings, 2 replies; 14+ messages in thread
From: David Glasser @ 2017-09-28 23:06 UTC (permalink / raw)
To: 28637
MELPA includes a :commit field in its
packages (https://github.com/melpa/package-build/pull/6). You can use
this to tell if MELPA has processed a recently-merged change. This
commit adds that metadata to the package description buffer.
* lisp/emacs-lisp/package.el: Display commit in package description
---
lisp/emacs-lisp/package.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index 8b101c1323..dd05c70dc8 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -2260,6 +2260,7 @@ Otherwise no newline is inserted."
(archive (if desc (package-desc-archive desc)))
(extras (and desc (package-desc-extras desc)))
(homepage (cdr (assoc :url extras)))
+ (commit (cdr (assoc :commit extras)))
(keywords (if desc (package-desc--keywords desc)))
(built-in (eq pkg-dir 'builtin))
(installable (and archive (not built-in)))
@@ -2332,6 +2333,8 @@ Otherwise no newline is inserted."
(and version
(package--print-help-section "Version"
(package-version-join version)))
+ (when commit
+ (package--print-help-section "Commit" commit))
(when desc
(package--print-help-section "Summary"
(package-desc-summary desc)))
--
2.14.1
^ permalink raw reply related [flat|nested] 14+ messages in thread* bug#28637: Display commit in package description, if available
2017-09-28 23:06 bug#28637: [PATCH] Display commit in package description, if available David Glasser
@ 2017-10-10 19:35 ` David Glasser
2017-10-10 20:07 ` Eli Zaretskii
2017-10-10 22:40 ` bug#28637: [PATCH] " Noam Postavsky
1 sibling, 1 reply; 14+ messages in thread
From: David Glasser @ 2017-10-10 19:35 UTC (permalink / raw)
To: 28637
Can I confirm that this went through successfully? Should I be
bringing up this patch on a different email list?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: Display commit in package description, if available
2017-10-10 19:35 ` bug#28637: " David Glasser
@ 2017-10-10 20:07 ` Eli Zaretskii
2017-10-10 22:05 ` David Glasser
0 siblings, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2017-10-10 20:07 UTC (permalink / raw)
To: David Glasser; +Cc: 28637
> From: David Glasser <glasser@davidglasser.net>
> Date: Tue, 10 Oct 2017 12:35:58 -0700
>
> Can I confirm that this went through successfully?
AFAICT, no one has reviewed this yet.
> Should I be bringing up this patch on a different email list?
This is the right place, just keep pinging until the patch is
reviewed.
Thanks.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: Display commit in package description, if available
2017-10-10 20:07 ` Eli Zaretskii
@ 2017-10-10 22:05 ` David Glasser
0 siblings, 0 replies; 14+ messages in thread
From: David Glasser @ 2017-10-10 22:05 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 28637
OK, sure!
I think this is a pretty minimal-impact change which makes the
experience of using melpa a lot better. I frequently send PRs to
packages that I fetch via melpa, and once I get the "merged"
notification, I want to be able to tell whether or not my change is
available in the melpa build.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
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 22:40 ` Noam Postavsky
2017-10-10 22:46 ` David Glasser
1 sibling, 1 reply; 14+ messages in thread
From: Noam Postavsky @ 2017-10-10 22:40 UTC (permalink / raw)
To: David Glasser; +Cc: 28637
David Glasser <glasser@davidglasser.net> writes:
> MELPA includes a :commit field in its
> packages (https://github.com/melpa/package-build/pull/6). You can use
> this to tell if MELPA has processed a recently-merged change. This
> commit adds that metadata to the package description buffer.
Code looks fine, but could you post a "before and after" picture please?
I'm wondering if it might make sense to abbreviate the hash.
> * lisp/emacs-lisp/package.el: Display commit in package description
I think you should have a period at the end of sentence though.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-10 22:40 ` bug#28637: [PATCH] " Noam Postavsky
@ 2017-10-10 22:46 ` David Glasser
2017-10-11 1:16 ` Noam Postavsky
0 siblings, 1 reply; 14+ messages in thread
From: David Glasser @ 2017-10-10 22:46 UTC (permalink / raw)
To: Noam Postavsky; +Cc: 28637
On Tue, Oct 10, 2017 at 3:40 PM, Noam Postavsky
<npostavs@users.sourceforge.net> wrote:
> David Glasser <glasser@davidglasser.net> writes:
>
>> MELPA includes a :commit field in its
>> packages (https://github.com/melpa/package-build/pull/6). You can use
>> this to tell if MELPA has processed a recently-merged change. This
>> commit adds that metadata to the package description buffer.
>
> Code looks fine, but could you post a "before and after" picture please?
> I'm wondering if it might make sense to abbreviate the hash.
Sure! Here's a randomly chosen melpa package's *Help* page:
```
archive-rpm is a new package.
Status: New from melpa -- Install
Archive: melpa
Version: 20171005.1548
Commit: 830158cfb3b43c85cfcb4bd5b92d4457d015c80a
Summary: RPM and CPIO support for archive-mode
Requires: emacs-24.4
This module adds support for RPM archives to archive-mode.
RPM files consist of metadata plus a compressed CPIO archive, so
this module relies on `archive-cpio'.
```
This is the "after" picture; the "before" picture lacks the Commit line.
Abbreviating the hash might be nice, but it seems like maybe that should be
the job of the code that creates the metadata (ie in melpa's package builder)
rather than the code that displays it.
>> * lisp/emacs-lisp/package.el: Display commit in package description
>
> I think you should have a period at the end of sentence though.
OK, a new version of the patch is below (is this the right way to send
a new version of the patch? I am not used to mail-based git
workflows):
From a4ebfa2ed35a620e4754399da8181caba13a1eb9 Mon Sep 17 00:00:00 2001
From: David Glasser <glasser@davidglasser.net>
Date: Thu, 28 Sep 2017 14:00:04 -0700
Subject: [PATCH] Display commit in package description, if available
MELPA includes a :commit field in its
packages (https://github.com/melpa/package-build/pull/6). You can use
this to tell if MELPA has processed a recently-merged change. This
commit adds that metadata to the package description buffer.
* lisp/emacs-lisp/package.el: Display commit in package description.
---
lisp/emacs-lisp/package.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index 8b101c1323..dd05c70dc8 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -2260,6 +2260,7 @@ Otherwise no newline is inserted."
(archive (if desc (package-desc-archive desc)))
(extras (and desc (package-desc-extras desc)))
(homepage (cdr (assoc :url extras)))
+ (commit (cdr (assoc :commit extras)))
(keywords (if desc (package-desc--keywords desc)))
(built-in (eq pkg-dir 'builtin))
(installable (and archive (not built-in)))
@@ -2332,6 +2333,8 @@ Otherwise no newline is inserted."
(and version
(package--print-help-section "Version"
(package-version-join version)))
+ (when commit
+ (package--print-help-section "Commit" commit))
(when desc
(package--print-help-section "Summary"
(package-desc-summary desc)))
^ permalink raw reply related [flat|nested] 14+ messages in thread* bug#28637: [PATCH] Display commit in package description, if available
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
0 siblings, 2 replies; 14+ messages in thread
From: Noam Postavsky @ 2017-10-11 1:16 UTC (permalink / raw)
To: David Glasser; +Cc: 28637
David Glasser <glasser@davidglasser.net> writes:
> Abbreviating the hash might be nice, but it seems like maybe that should be
> the job of the code that creates the metadata (ie in melpa's package builder)
> rather than the code that displays it.
Hmm, I'm not so sure about that, but looking at the result now I think
there's no need to abbreviate it anyway.
I think this should be okay to go to emacs-26; it's not strictly
speaking a bug fix, but it's obviously safe and this info is often
useful for package maintainers fielding bug reports, so it would be good
to have it more widely available. Eli?
> OK, a new version of the patch is below (is this the right way to send
> a new version of the patch? I am not used to mail-based git
> workflows):
Yup, that's fine. You can also use the -v option to git-format-patch in
order to make it more obvious that the patch is new. For small stuff
like this, it's not really important though.
I suppose you haven't assigned copyright for Emacs? No problem if not,
the patch is small enough to go in anyway, we just have to mark it.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-11 1:16 ` Noam Postavsky
@ 2017-10-11 4:14 ` David Glasser
2017-10-11 10:41 ` Eli Zaretskii
1 sibling, 0 replies; 14+ messages in thread
From: David Glasser @ 2017-10-11 4:14 UTC (permalink / raw)
To: Noam Postavsky; +Cc: 28637
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
On Oct 10, 2017 6:16 PM, "Noam Postavsky" <npostavs@users.sourceforge.net>
wrote:
I suppose you haven't assigned copyright for Emacs? No problem if not,
the patch is small enough to go in anyway, we just have to mark it.
I don't believe I have.
--dave
[-- Attachment #2: Type: text/html, Size: 778 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
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
1 sibling, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2017-10-11 10:41 UTC (permalink / raw)
To: Noam Postavsky; +Cc: glasser, 28637
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Tue, 10 Oct 2017 21:16:36 -0400
> Cc: 28637@debbugs.gnu.org
>
> I think this should be okay to go to emacs-26; it's not strictly
> speaking a bug fix, but it's obviously safe and this info is often
> useful for package maintainers fielding bug reports, so it would be good
> to have it more widely available. Eli?
Are we sure no feature parses this output, and might be confused by
the extra line?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-11 10:41 ` Eli Zaretskii
@ 2017-10-11 12:32 ` Noam Postavsky
2017-10-11 13:12 ` Eli Zaretskii
0 siblings, 1 reply; 14+ messages in thread
From: Noam Postavsky @ 2017-10-11 12:32 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: glasser, 28637
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Tue, 10 Oct 2017 21:16:36 -0400
>> Cc: 28637@debbugs.gnu.org
>>
>> I think this should be okay to go to emacs-26; it's not strictly
>> speaking a bug fix, but it's obviously safe and this info is often
>> useful for package maintainers fielding bug reports, so it would be good
>> to have it more widely available. Eli?
>
> Are we sure no feature parses this output, and might be confused by
> the extra line?
As far as I can tell, it's only used for the *Help* buffer, and nothing
parses that.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-11 12:32 ` Noam Postavsky
@ 2017-10-11 13:12 ` Eli Zaretskii
2017-10-23 23:58 ` Noam Postavsky
0 siblings, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2017-10-11 13:12 UTC (permalink / raw)
To: Noam Postavsky; +Cc: glasser, 28637
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: glasser@davidglasser.net, 28637@debbugs.gnu.org
> Date: Wed, 11 Oct 2017 08:32:43 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Noam Postavsky <npostavs@users.sourceforge.net>
> >> Date: Tue, 10 Oct 2017 21:16:36 -0400
> >> Cc: 28637@debbugs.gnu.org
> >>
> >> I think this should be okay to go to emacs-26; it's not strictly
> >> speaking a bug fix, but it's obviously safe and this info is often
> >> useful for package maintainers fielding bug reports, so it would be good
> >> to have it more widely available. Eli?
> >
> > Are we sure no feature parses this output, and might be confused by
> > the extra line?
>
> As far as I can tell, it's only used for the *Help* buffer, and nothing
> parses that.
Then it could be okay for emacs-26, if its addition is deemed
important enough.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-11 13:12 ` Eli Zaretskii
@ 2017-10-23 23:58 ` Noam Postavsky
2017-10-24 14:46 ` Eli Zaretskii
0 siblings, 1 reply; 14+ messages in thread
From: Noam Postavsky @ 2017-10-23 23:58 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: glasser, 28637
Eli Zaretskii <eliz@gnu.org> writes:
> Then it could be okay for emacs-26, if its addition is deemed
> important enough.
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.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-23 23:58 ` Noam Postavsky
@ 2017-10-24 14:46 ` Eli Zaretskii
2017-10-24 23:26 ` Noam Postavsky
0 siblings, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2017-10-24 14:46 UTC (permalink / raw)
To: Noam Postavsky; +Cc: glasser, 28637
> 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.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#28637: [PATCH] Display commit in package description, if available
2017-10-24 14:46 ` Eli Zaretskii
@ 2017-10-24 23:26 ` Noam Postavsky
0 siblings, 0 replies; 14+ messages in thread
From: Noam Postavsky @ 2017-10-24 23:26 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: glasser, 28637
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
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2017-10-24 23:26 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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).