From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Juri Linkov <juri@jurta.org>, Sam Steingold <sds@gnu.org>,
emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r111349: * lisp/progmodes/cperl-mode.el (cperl-calculate-indent): Do not stagger
Date: Fri, 28 Dec 2012 09:49:47 +0900 [thread overview]
Message-ID: <877go3ov9w.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87k3s3rwhc.fsf@yandex.ru>
Dmitry Gutov writes:
> Juri Linkov <juri@jurta.org> writes:
>
> >>> - from 109911 (see the new test).
> >>> + from Bug#109911 (see the new test).
> >>
> >> This change is inaccurate. 109911 is a Bazaar revision, not a bug number.
> >
> > To avoid ambiguity and misunderstanding revisions should have a prefix
> > similar to bug numbers, e.g. revno#109911 or revno:109911.
>
> Thanks, will do next time.
> I guess I'm used to Git, where you don't usually prefix commit ids with
> anything.
Are those strings valid syntax for referencing bzr revisions (eg in
log or checkout)? It would be best to standardize on valid syntax
(eg, for cut and paste). Only rarely useful, I suppose, but ...
next prev parent reply other threads:[~2012-12-28 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ToH53-0003nX-W3@vcs.savannah.gnu.org>
2012-12-27 18:24 ` /srv/bzr/emacs/trunk r111349: * lisp/progmodes/cperl-mode.el (cperl-calculate-indent): Do not stagger Dmitry Gutov
2012-12-27 19:39 ` Juri Linkov
2012-12-27 20:12 ` Sam Steingold
2012-12-27 21:55 ` Dmitry Gutov
2012-12-27 22:45 ` bug-reference and revisions Juri Linkov
2012-12-27 23:20 ` Dmitry Gutov
2012-12-28 0:49 ` Stephen J. Turnbull [this message]
2012-12-28 4:36 ` /srv/bzr/emacs/trunk r111349: * lisp/progmodes/cperl-mode.el (cperl-calculate-indent): Do not stagger Xue Fuqiao
2012-12-28 6:49 ` Stephen J. Turnbull
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=877go3ov9w.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=sds@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).