all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Harald Hanche-Olsen <hanche@math.ntnu.no>
Cc: 12441@debbugs.gnu.org
Subject: bug#12441: Acknowledgement (24.2.50; emacs-bzr-version is not reliable)
Date: Fri, 14 Sep 2012 12:16:20 -0400	[thread overview]
Message-ID: <rzk3vw60mj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20120914.140514.1206889292717438125.hanche@math.ntnu.no> (Harald Hanche-Olsen's message of "Fri, 14 Sep 2012 14:05:14 +0200 (CEST)")

Harald Hanche-Olsen wrote:

> I have a local (heavyweight) repository that tracks trunk from the
> official emacs repository. The tip of that branch, at the time when
> I compiled emacs, was indeed revision 110013, as reported in the
> emacs-bzr-version variable.
>
>>From my local trunk I did
>
> bzr checkout --lightweight -r 109703 . ../r109703
>
> and then I cd'd into that directory and compiled emacs there.
> The resulting emacs shows revision 110013 in emacs-bzr-version.

BTW, so does:

bzr revno

unless you add --tree.

> I have not checked if doing a heavyweight checkout would yield the
> same result.

No, that works fine. It also takes exactly the same time to checkout and
produces a directory with exactly the same size (assuming a shared
repository) as the lightweight case. So I'd suggest forgetting about
lightweight checkouts.

I'd say what you're doing is outside the simple uses cases that
emacs-bzr-version (which is really just a minor convenience for bug
reports) is for. You obviously know what revision you are using since
you specified it manually.

There's no way to get the real revision number of your lightweight
checkout without running a bzr command. But I do not want to run any
form of external command to find emacs-bzr-version, since it happens
during dumping, etc.

It would perhaps be better if we returned nil rather the wrong answer in
your case, but I see no way even to do that.

Lightweight checkouts with and without -r differ only in their dirstate
files. So perhaps the information is buried in here if someone wants to
dig it out. But there is no simple version string AFAICS.


Which is a long-winded way of saying this gets a "wontfix" from me.





  reply	other threads:[~2012-09-14 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  9:52 bug#12441: 24.2.50; emacs-bzr-version is not reliable Harald Hanche-Olsen
     [not found] ` <handler.12441.B.134761641913163.ack@debbugs.gnu.org>
2012-09-14 12:05   ` bug#12441: Acknowledgement (24.2.50; emacs-bzr-version is not reliable) Harald Hanche-Olsen
2012-09-14 16:16     ` Glenn Morris [this message]
2012-09-14 17:02       ` Harald Hanche-Olsen
2012-09-14 19:32         ` Stefan Monnier
2012-09-14 23:22           ` bug#12441: emacs-bzr-version is not reliable Glenn Morris
2012-09-15  0:35             ` Glenn Morris
2012-09-15  1:12               ` Glenn Morris
2012-09-14 23:28 ` bug#12441: 24.2.50; " Andy Moreton

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=rzk3vw60mj.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=12441@debbugs.gnu.org \
    --cc=hanche@math.ntnu.no \
    /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.