all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#4879: Crash in xmenu_show
Date: Wed, 11 Nov 2009 08:11:46 -0700	[thread overview]
Message-ID: <hdek77$ief$3@ger.gmane.org> (raw)
In-Reply-To: <83y6miaeqn.fsf@gnu.org>

Eli Zaretskii wrote:
>> From: Juri Linkov <juri@jurta.org>
>> Cc: 4879@emacsbugs.donarmstrong.com
>> Date: Fri, 06 Nov 2009 23:10:27 +0200
...
>> 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.

3rd party distributions may not use the same procedure as you, and they seem
to generate a fair number of bug reports.

-- 
Kevin Rodgers
Denver, Colorado, USA







  reply	other threads:[~2009-11-11 15:11 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
2009-11-11 15:11       ` Kevin Rodgers [this message]
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='hdek77$ief$3@ger.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=4879@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.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.