From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: `about-emacs' - what about the revno?
Date: Tue, 31 Aug 2010 10:22:32 +0200 [thread overview]
Message-ID: <jwv62yrjj01.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87d3szra8f.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Tue, 31 Aug 2010 00:45:04 +0200")
> So for what we use the revision information? How it helps to know which
> was the last commit from trunk included on a build?
It relates his code to the one in our repository, i.e. to something
about which we know something.
> What's the use case?
When he reports a bug that's supposedly been fixed recently, we can know
whether his report is because he uses an old version that doesn't yet
have the patch applied. This has already happened a few times over the
last few months.
That's the only use-case I know for a "revision information".
> Having the revision-id you can test if the sources comes straight from
> Savannah. If it doesn't, the bug is his business, as we have no way of
> figuring out what changes his build contains.
Yes, that's also a valid approach.
> A revision-id uniquely identifies the state of a branch, the revision
> number does not. For what we need a number that may or may not
> correspond to some commit on `trunk'?
I never suggested to use just "bzr revno", instead I suggest to use "the
revno on the trunk of the common ancestor". It also uniquely identifies
a particular revision, and moreover it's a revision which we know.
And being a revno makes it slightly more convenient since you can more
easily (i.e. in your own head) compare two revnos to know whether it
contains a particular patch.
Stefan
prev parent reply other threads:[~2010-08-31 8:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 15:38 `about-emacs' - what about the revno? Drew Adams
2010-08-28 15:57 ` 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 [this message]
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=jwv62yrjj01.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.