From: Jeff King <peff@peff.net>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
Radu Rendec <radu.rendec@ines.ro>,
Denys Fedoryschenko <denys@visp.net.lb>,
netdev <netdev@vger.kernel.org>,
git@vger.kernel.org
Subject: Re: htb parallelism on multi-core platforms
Date: Thu, 23 Apr 2009 16:09:32 -0400 [thread overview]
Message-ID: <20090423200932.GB3056@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0904232136040.13796@ask.diku.dk>
On Thu, Apr 23, 2009 at 09:47:05PM +0200, Jesper Dangaard Brouer wrote:
>>> Is there any easy git way to figure out which release this commit got
>>> into?
>>
>> I guess git-describe, but I prefer clicking at the "raw" (X-Git-Tag):
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2
>
> I think I prefer the command line edition "git-describe". But it seems
> that the two approaches gives a different results.
> (Cc'ing the git mailing list as they might know the reason)
You want "git describe --contains". The default mode for describe is
"you are at tag $X, plus $N commits, and by the way, the sha1 is $H"
(shown as "$X-$N-g$H").
The default mode is useful for generating a unique semi-human-readable
version number (e.g., to be included in your builds).
-Peff
prev parent reply other threads:[~2009-04-23 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090423184319.GB2756@ami.dom.local>
[not found] ` <Pine.LNX.4.64.0904232103390.13488@ask.diku.dk>
[not found] ` <20090423191455.GC2756@ami.dom.local>
2009-04-23 19:47 ` htb parallelism on multi-core platforms Jesper Dangaard Brouer
2009-04-23 20:00 ` Jarek Poplawski
2009-04-23 20:09 ` Jeff King [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090423200932.GB3056@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=denys@visp.net.lb \
--cc=git@vger.kernel.org \
--cc=hawk@diku.dk \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=radu.rendec@ines.ro \
/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.
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 NNTP newsgroup(s).