all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: 4879@emacsbugs.donarmstrong.com
Subject: bug#4879: Crash in xmenu_show
Date: Sat, 07 Nov 2009 11:03:28 +0200	[thread overview]
Message-ID: <83y6miaeqn.fsf@gnu.org> (raw)
In-Reply-To: <87k4y3l5jh.fsf@mail.jurta.org>

> From: Juri Linkov <juri@jurta.org>
> Cc: 4879@emacsbugs.donarmstrong.com
> Date: Fri, 06 Nov 2009 23:10:27 +0200
> 
> > What does it mean, exactly?  Why didn't you send the report using "M-x
> > report-emacs-bug RET", where all this information is automatically
> > included?
> 
> `M-x report-emacs-bug RET' includes irrelevant information

OTOH, it includes some very relevant one - the exact way you
configured Emacs for the build, and the language environment in which
you invoked Emacs.  These are there for a reason, and if you don't
want to send the whole report for some reason, at least send these
parts of it.  How can we possibly educate users to use this facility
if the developers themselves don't?

> the date
> it inserts in the version string is the date of compilation that
> provides no help to reproduce the bug.  Is it possible to replace it
> with the date of the last CVS checkout/update that says exactly what
> state of the code repository contains the bug?

Everything's possible -- this is software.  You could write code that
looks in the ChangeLog files for the latest log entries in src/,
lisp/, and leim/, for example.  Or the code could look at the time
stamp of some CVS/Template file (in any directory) -- but this needs
to be changed for those who use VCs other than CVS, and for everybody
when we switch to bzr.

Personally, I never build without "cvs update", so the build time is
almost exactly the checkout time.





  reply	other threads:[~2009-11-07  9:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 10:49 bug#4879: Crash in xmenu_show Juri Linkov
2009-11-06 11:50 ` Eli Zaretskii
2009-11-06 15:11   ` Jan Djärv
2009-11-06 21:06     ` Juri Linkov
2009-11-06 21:10   ` Juri Linkov
2009-11-07  9:03     ` Eli Zaretskii [this message]
2009-11-11 15:11       ` Kevin Rodgers
2009-11-11 16:39     ` Stefan Monnier
2009-11-14  4:39       ` Glenn Morris
2009-11-14  7:10         ` Stefan Monnier
     [not found] <87aayzchne.fsf@stupidchicken.com>
2009-11-08  3:43 ` Stefan Monnier
2009-11-08  5:02   ` Chong Yidong
2009-11-08 15:07     ` Stefan Monnier
2009-11-09  0:49       ` Juri Linkov

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=83y6miaeqn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=4879@emacsbugs.donarmstrong.com \
    --cc=juri@jurta.org \
    /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.