From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 30446@debbugs.gnu.org
Subject: [bug#30446] [PATCH 1/3] gnu: Add ifdtool.
Date: Tue, 13 Feb 2018 22:00:33 -0500 [thread overview]
Message-ID: <20180214030033.GB2349@jasmine.lan> (raw)
In-Reply-To: <87po58mudi.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Tue, Feb 13, 2018 at 10:50:49PM +0100, Marius Bakke wrote:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
> > Hi Leo,
> >
> > On Tue, 13 Feb 2018 14:18:43 -0500
> > Leo Famulari <leo@famulari.name> wrote:
> >
> >> I notice the Git repo has tagged versions. If the latest one is
> >> inappropriate to build from, please use it in the git-version like this:
> >
> > How do I find out which commit corresponds to a tag (or which commits are
> > not in the 4.7 tag) ?
>
> You can use the tag name in the (revision ...) field (see e.g. libvpx).
>
> To find which commits are not in a given tag, use something along the
> lines of...
>
> $ git log --format=oneline v4.7..master
Also, `git describe --contains $commit` will tell you the latest tag
that contains the commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-14 3:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 18:00 [bug#30446] [PATCH 0/3] Add Intel ME tools Danny Milosavljevic
2018-02-13 18:01 ` [bug#30446] [PATCH 1/3] gnu: Add ifdtool Danny Milosavljevic
2018-02-13 18:01 ` [bug#30446] [PATCH 2/3] gnu: Add intelmetool Danny Milosavljevic
2018-02-13 19:20 ` Leo Famulari
2018-02-13 20:36 ` Danny Milosavljevic
2018-02-14 3:06 ` Leo Famulari
2018-02-13 18:01 ` [bug#30446] [PATCH 3/3] gnu: Add me-cleaner Danny Milosavljevic
2018-02-13 19:21 ` Leo Famulari
2018-02-13 21:29 ` Danny Milosavljevic
2018-02-13 19:18 ` [bug#30446] [PATCH 1/3] gnu: Add ifdtool Leo Famulari
2018-02-13 20:37 ` Danny Milosavljevic
2018-02-13 21:50 ` Marius Bakke
2018-02-14 3:00 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180214030033.GB2349@jasmine.lan \
--to=leo@famulari.name \
--cc=30446@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).