From: Eli Zaretskii <eliz@gnu.org>
To: esr@thyrsus.com
Cc: emacs-devel@gnu.org
Subject: Re: The fixes-bug field
Date: Sat, 18 Jan 2014 09:51:50 +0200 [thread overview]
Message-ID: <8338kllobt.fsf@gnu.org> (raw)
In-Reply-To: <20140117202957.GA27014@thyrsus.com>
> Date: Fri, 17 Jan 2014 15:29:57 -0500
> From: "Eric S. Raymond" <esr@thyrsus.com>
> Cc: emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org>:
> > > From: esr@thyrsus.com (Eric S. Raymond)
> > > Date: Thu, 16 Jan 2014 09:15:06 -0500 (EST)
> > >
> > > Eli Zaretskii:
> > > "revisions 103939.1.41..103939.1.44 (inclusive)"
> > If that doesn't give you the info you want, please tell what else do
> > you need (e.g., bzr revision IDs are easy, if you need them).
>
> High-level, what I want is a VCS-independent was to describe that range
> of commits.
>
> Unless there's an easy synoptic description of that range in English
> (which would be preferable, but seems unlikely)
Sorry, I don't understand what needs to be explained. Those are trunk
revision numbers, they are of the "dotted" NNN.X.Y form because they
came from a merge commit of another branch. That branch was Paul
Eggert's local feature branch. But the revisions are still accessible
on the trunk using those very numbers (that's why I made a point of
specifying _trunk_ revno numbers, although the commit was on the
emacs-23 branch -- I knew that trunk will live forever).
So whatever you need to know about these revisions you can see using
these numbers, for example:
bzr log -c 103939.1.41
> I'll need the committer and timestamp of 103939.1.41 and 103939.1.44
> so I can express those as action stamps.
Since both the committer and the time stamp are in the bzr revision
ID, here you go:
bzr log --include-merged --long --show-ids -r 103939.1.41..103939.1.44 | fgrep revision-id
revision-id: eggert@cs.ucla.edu-20110425213439-wok7h5v3k2w6ypke
revision-id: eggert@cs.ucla.edu-20110425194022-kykvykyv2w7o4arq
revision-id: eggert@cs.ucla.edu-20110425073357-1egaqnih5jn5juxe
revision-id: eggert@cs.ucla.edu-20110425071446-kj82psqnn82sjnsb
You want the first 2 parts of the revision IDs, before the 2nd dash.
next prev parent reply other threads:[~2014-01-18 7:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 14:15 The fixes-bug field Eric S. Raymond
2014-01-16 17:11 ` Eli Zaretskii
2014-01-17 20:29 ` Eric S. Raymond
2014-01-18 7:51 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 14:13 Eric S. Raymond
2014-01-16 16:13 ` Stefan Monnier
2014-01-16 16:30 ` Eric S. Raymond
2014-01-16 16:55 ` Eli Zaretskii
2014-01-16 17:54 ` Glenn Morris
2014-01-16 18:09 ` Eric S. Raymond
2014-01-16 18:38 ` Darren Hoo
2014-01-16 19:32 ` Stefan Monnier
2014-01-16 20:06 ` Glenn Morris
2014-01-16 21:30 ` Eli Zaretskii
2014-01-16 21:24 ` Eli Zaretskii
2014-01-16 18:55 ` Paul Eggert
2014-01-16 19:13 ` Glenn Morris
2014-01-16 20:25 ` Paul Eggert
2014-01-16 18:08 ` Eric S. Raymond
2014-01-16 18:36 ` Eli Zaretskii
2014-01-16 20:04 ` Eric S. Raymond
2014-01-16 21:29 ` Eli Zaretskii
2014-01-16 21:47 ` Eric S. Raymond
2014-01-17 7:32 ` Eli Zaretskii
2014-01-17 7:58 ` Paul Eggert
2014-01-17 8:04 ` Jarek Czekalski
2014-01-17 9:21 ` Yuri Khan
2014-01-17 14:31 ` Stefan Monnier
2014-01-17 15:57 ` Lars Ingebrigtsen
2014-01-17 16:12 ` Stefan Monnier
2014-01-17 17:20 ` Lars Ingebrigtsen
2014-01-18 9:19 ` Jarek Czekalski
2014-01-18 16:02 ` Lars Ingebrigtsen
2014-01-17 13:16 ` Eric S. Raymond
2014-01-17 13:55 ` Eli Zaretskii
2014-01-17 14:26 ` Stefan Monnier
2014-01-16 17:00 ` Glenn Morris
2014-01-16 17:22 ` Achim Gratz
2014-01-16 17:57 ` Glenn Morris
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=8338kllobt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
/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.