From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: ofv@wanadoo.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Setting the value of `emacs-bzr-version' also from a git checkout
Date: Sat, 12 Oct 2013 14:37:07 +0300 [thread overview]
Message-ID: <83fvs6ra8s.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0ghC5LjPwWKgporpi84=yLrK2EM3kUthQATZVptADrAeA@mail.gmail.com>
> Date: Sat, 12 Oct 2013 13:06:40 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Óscar Fuentes <ofv@wanadoo.es>,
> Emacs development discussions <emacs-devel@gnu.org>
>
> >> Of course, but that would require the user to have bzr installed, just
> >> to get the revnos from the revids.
> >
> > Emacs developers and maintainers already have bzr installed.
>
> But there are probably many people (like myself) who would like use
> only git for all version control tasks. And that's already possible.
> What I want to do now is something very simple: getting the bzr revnos
> out of the git notes, in order to produce binaries which included both
> the revno and the revid.
The bzr revision information is for the maintainers to be able to
correlate reported problems with Emacs development. For that purpose,
having the revision-id is enough.
As I said, if the revision numbers are also available, that is
better. But it's not a requirement, and I have no idea why would a
user need to know the revision number.
next prev parent reply other threads:[~2013-10-12 11:37 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
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 [this message]
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=83fvs6ra8s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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.