From: Eli Zaretskii <eliz@gnu.org>
To: Stromeko@nexgo.de
Cc: 33328@debbugs.gnu.org
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Thu, 22 Nov 2018 21:31:02 +0200 [thread overview]
Message-ID: <83bm6ghpu1.fsf@gnu.org> (raw)
In-Reply-To: <83d0qwhq7n.fsf@gnu.org> (message from Eli Zaretskii on Thu, 22 Nov 2018 21:22:52 +0200)
> Date: Thu, 22 Nov 2018 21:22:52 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 33328@debbugs.gnu.org
>
> > From: Achim Gratz <Stromeko@nexgo.de>
> > Date: Thu, 22 Nov 2018 20:14:56 +0100
> >
> > Michael Albinus writes:
> > > A version number is not sufficient. It depends, which branch is checked
> > > out. See for example
> >
> > It is quite useless to ask which branch a given commit is on, since it
> > could be on any number of branches, only some of which might be shared
> > between your repo and the repo of the reporter.
>
> In general, yes. But not in Emacs development, not with public
> development branches anyway.
And, btw, if you read carefully what Michael wrote above, you will see
that he is not asking what branch a given commit is on, he is asking a
different question.
next prev parent reply other threads:[~2018-11-22 19:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 22:19 bug#33328: 27.0.50; Extend Emacs bug report Michael Albinus
2018-11-10 7:47 ` Eli Zaretskii
2018-11-10 8:57 ` Michael Albinus
2018-11-10 9:49 ` Eli Zaretskii
2018-11-10 15:09 ` Michael Albinus
2018-11-15 17:45 ` Glenn Morris
2018-11-15 20:31 ` Michael Albinus
2018-11-20 19:00 ` Glenn Morris
2018-11-21 12:46 ` Michael Albinus
2018-11-22 18:52 ` Glenn Morris
2018-11-22 19:08 ` Eli Zaretskii
2018-11-22 19:14 ` Achim Gratz
2018-11-22 19:22 ` Eli Zaretskii
2018-11-22 19:31 ` Eli Zaretskii [this message]
2018-11-22 19:36 ` Achim Gratz
2018-11-22 21:52 ` Michael Albinus
2018-11-25 11:21 ` Achim Gratz
2018-11-25 11:46 ` Michael Albinus
2018-11-23 8:14 ` Eli Zaretskii
2018-11-22 19:32 ` Achim Gratz
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=83bm6ghpu1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33328@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
/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.