all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Wed, 11 Oct 2017 08:32:43 -0400	[thread overview]
Message-ID: <87wp41c1as.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83wp42nf01.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 11 Oct 2017 13:41:18 +0300")

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.





  reply	other threads:[~2017-10-11 12:32 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 [this message]
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

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=87wp41c1as.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.