all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 33328@debbugs.gnu.org
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Sat, 10 Nov 2018 09:47:36 +0200	[thread overview]
Message-ID: <83d0rdbch3.fsf@gnu.org> (raw)
In-Reply-To: <87pnvdgah9.fsf@gmx.de> (message from Michael Albinus on Fri, 09 Nov 2018 23:19:30 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Fri, 09 Nov 2018 23:19:30 +0100
> 
> Working on Emacs branches, I'd like to see branch information in the bug
> report. It could look like in this report, see the "Repository branch"
> line. The respective patch is appended.
> 
> Is it OK to push to master?

You pushed ignoring-errors to the functions that return the revision
and the branch, and I wonder whether that is a good idea.  Those
functions are useful on their own right, and their doc strings say
nothing about the situation where something goes wrong with the Git
invocation or any other calamities.

Thanks.





  reply	other threads:[~2018-11-10  7:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 22:19 bug#33328: 27.0.50; Extend Emacs bug report Michael Albinus
2018-11-10  7:47 ` Eli Zaretskii [this message]
2018-11-10  8:57   ` Michael Albinus
2018-11-10  9:49     ` Eli Zaretskii
2018-11-10 15:09       ` Michael Albinus
2018-11-15 17:45 ` Glenn Morris
2018-11-15 20:31   ` Michael Albinus
2018-11-20 19:00     ` Glenn Morris
2018-11-21 12:46       ` Michael Albinus
2018-11-22 18:52         ` Glenn Morris
2018-11-22 19:08           ` Eli Zaretskii
2018-11-22 19:14         ` Achim Gratz
2018-11-22 19:22           ` Eli Zaretskii
2018-11-22 19:31             ` Eli Zaretskii
2018-11-22 19:36               ` Achim Gratz
2018-11-22 21:52                 ` Michael Albinus
2018-11-25 11:21                   ` Achim Gratz
2018-11-25 11:46                     ` Michael Albinus
2018-11-23  8:14                 ` Eli Zaretskii
2018-11-22 19:32             ` Achim Gratz

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=83d0rdbch3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33328@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.