all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Setting the value of `emacs-bzr-version' also from a git checkout
Date: Tue, 1 Oct 2013 23:15:17 +0200	[thread overview]
Message-ID: <CAH8Pv0imkSwey8JS_xAE7Cp4ENZ5phV1zXhSMQPL6ghX10FW7Q@mail.gmail.com> (raw)
In-Reply-To: <87pprokewg.fsf@wanadoo.es>

On Tue, Oct 1, 2013 at 8:46 PM, Óscar Fuentes <ofv@wanadoo.es> wrote:
> Dani Moncayo <dmoncayo@gmail.com> writes:
>
>> But the final goal would be to make `emacs-bzr-version' get the
>> correct value also when building emacs from the official git repo.
>> And since its value includes both the bzr revno and the bzr revision
>> ID (e.g. "114456 rgm@gnu.org-20130925101746-8kz06nvtpjms0hy3"), the
>> notes stored in the git repo are insufficient (they lack the bzr
>> revno).
>
> Just teach the build scripts to not require the revision number.

Not sure what you mean.  AFAIK, the build scripts don't require it.

> From the revision id whoever reads the bug report can get the revision
> number (for a given branch.) Actually, if you look only to the revision
> number you can end wasting your time, because you don't know which
> branch was used to build that Emacs.

Yes I know, the bzr revision number is always relative to some bzr
branch, while the bzr revid is universally unique.  But my point is
that `emacs-bzr-version' gives both of them (on an Emacs built from a
bzr branch), and everyone in these lists prefer the bzr revno, because
is shorter/simpler.

Therefore, what I'd like is that "emacs-bzr-version" gave the exact
same string from an Emacs built from either bzr-trunk or git-master.

-- 
Dani Moncayo



  reply	other threads:[~2013-10-01 21:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 16:45 Setting the value of `emacs-bzr-version' also from a git checkout (was: Emacs trunk binary on Dropbox) Dani Moncayo
2013-10-01 17:04 ` Setting the value of `emacs-bzr-version' also from a git checkout Óscar Fuentes
2013-10-01 17:45 ` Andreas Schwab
2013-10-01 18:37   ` Dani Moncayo
2013-10-01 18:46     ` Óscar Fuentes
2013-10-01 21:15       ` Dani Moncayo [this message]
2013-10-02  0:22         ` Stefan Monnier
2013-10-02 14:36           ` Josh
2013-10-12 10:22           ` Dani Moncayo
2013-10-12 10:33             ` Eli Zaretskii
2013-10-12 10:42               ` Dani Moncayo
2013-10-12 10:51                 ` Óscar Fuentes
2013-10-12 10:58                   ` Dani Moncayo
2013-10-12 11:16                   ` Dani Moncayo
2013-10-12 11:40                     ` Eli Zaretskii
2013-10-12 12:04                       ` Dani Moncayo
2013-10-12 19:04                     ` Óscar Fuentes
2013-10-12 20:36                       ` Juanma Barranquero
2013-10-12 20:51                         ` Óscar Fuentes
2013-10-12 20:57                           ` Juanma Barranquero
2013-10-12 21:16                             ` Óscar Fuentes
2013-10-12 21:33                               ` Juanma Barranquero
2013-10-12 20:56                       ` Stefan Monnier
2013-10-12 21:25                       ` Dani Moncayo
2013-10-12 21:38                         ` Óscar Fuentes
2013-10-12 10:58                 ` Eli Zaretskii
2013-10-12 11:06                   ` Dani Moncayo
2013-10-12 11:37                     ` Eli Zaretskii
2013-10-13 20:49             ` Dani Moncayo
2013-10-13 22:16               ` Glenn Morris
2013-10-14  6:38                 ` Dani Moncayo
  -- strict thread matches above, loose matches on Subject: below --
2013-10-01 20:23 Dani Moncayo

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=CAH8Pv0imkSwey8JS_xAE7Cp4ENZ5phV1zXhSMQPL6ghX10FW7Q@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --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.