bug#28637: [PATCH] Display commit in package description, if available

[Noam Postavsky <npostavs@users.sourceforge.net>]

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.