From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: `about-emacs' - what about the revno?
Date: Sat, 28 Aug 2010 08:38:15 -0700 [thread overview]
Message-ID: <FAC6F426B33043ED8B06963BC6DC262A@us.oracle.com> (raw)
When a bug that I filed gets fixed, sometimes the developer who fixes it lets me
know which "revno" it is fixed in. E.g. "This bug is now fixed (revno 101110)."
I do not build Emacs myself, and I have no idea what the "revno" corresponds to
or how/where to find it in an existing Emacs build (binary).
When I do `C-h C-a', or when I submit a bug, I see only an identifier like this:
GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2010-08-16 on 3249CTO
If the "revno" is important info for identifying an Emacs build, then perhaps we
should include it in such user-facing info. If not, then perhaps developers
could refer in some other way (by date?) to the code that contains a given fix.
next reply other threads:[~2010-08-28 15:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 15:38 Drew Adams [this message]
2010-08-28 15:57 ` `about-emacs' - what about the revno? Eli Zaretskii
2010-08-28 16:05 ` Drew Adams
2010-08-28 16:13 ` Eli Zaretskii
2010-08-28 16:34 ` Jason Rumney
2010-08-28 17:12 ` Óscar Fuentes
2010-08-28 19:06 ` Christoph
2010-08-29 4:56 ` Teemu Likonen
2010-08-30 15:41 ` Stefan Monnier
2010-08-30 16:22 ` Lennart Borgman
2010-08-30 16:27 ` Eli Zaretskii
2010-08-30 17:50 ` Eli Zaretskii
2010-08-30 19:20 ` Óscar Fuentes
2010-08-30 22:07 ` Stefan Monnier
2010-08-31 6:34 ` Andreas Schwab
2010-08-31 10:35 ` Stefan Monnier
2010-08-31 10:41 ` Andreas Schwab
2010-08-31 13:01 ` Stefan Monnier
2010-08-31 20:08 ` Óscar Fuentes
2010-09-01 6:20 ` Stefan Monnier
2010-08-31 14:02 ` Miles Bader
2010-08-31 16:56 ` Eli Zaretskii
2010-09-01 6:25 ` Stefan Monnier
2010-09-01 6:42 ` Eli Zaretskii
2010-09-01 7:45 ` Stefan Monnier
2010-09-01 8:41 ` Eli Zaretskii
2010-08-31 16:58 ` Eli Zaretskii
2010-08-30 17:39 ` Óscar Fuentes
2010-08-30 17:58 ` Lennart Borgman
2010-08-30 22:08 ` Stefan Monnier
2010-08-30 22:45 ` Óscar Fuentes
2010-08-31 8:22 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FAC6F426B33043ED8B06963BC6DC262A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).