From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: linux-c-programming@vger.kernel.org
Subject: Git tags
Date: Thu, 03 Apr 2008 15:54:55 +0200 [thread overview]
Message-ID: <47F4E1AF.5060509@visionsystems.de> (raw)
Hi all,
I don't really know where to post this question. Why, if I check out the
2.6.24.4 kernel (2.6.24.4 tag
http://git2.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=16c64cac7d9c6a503f49887219c4fe675e7d43d9)
from the stable git tree, I get "dirty" added to my kernel version after
compilation? The 2.6.24.4 is stable as far as I understand.
I have already searched for this info and looked through some tutorials
like http://linux.yyz.us/git-howto.html, but I didn't find any info that
would answer my question.
Thank you in advance.
Best regards,
Yegor
next reply other threads:[~2008-04-03 13:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:54 Yegor Yefremov [this message]
2008-04-03 14:32 ` Git tags Andre Haupt
2008-04-03 14:40 ` Yegor Yefremov
2008-04-03 14:47 ` Andre Haupt
2008-04-03 14:55 ` Andre Haupt
-- strict thread matches above, loose matches on Subject: below --
2018-11-29 11:11 Git Tags Stefanie Leisestreichler
2018-11-29 11:56 ` Mateusz Loskot
2018-11-29 13:40 ` Randall S. Becker
2018-11-29 13:45 ` Mateusz Loskot
2018-11-29 15:09 ` Ævar Arnfjörð Bjarmason
2017-06-16 1:07 Git tags Oliver Beattie
2017-06-16 1:14 ` Daniel Kahn Gillmor
2017-06-16 2:44 ` Jason A. Donenfeld
2017-06-16 12:07 ` Martin Eskdale Moen
2017-06-16 12:08 ` Jason A. Donenfeld
2017-06-16 12:12 ` Martin Eskdale Moen
2017-06-16 12:23 ` Jason A. Donenfeld
2017-06-16 16:40 ` Oliver Beattie
2009-12-04 11:27 Martyn Welch
2009-12-09 0:19 ` Geoff Levand
2007-10-22 11:24 GIT tags Iqbal
2007-10-22 11:35 ` Felipe Balbi
2007-10-22 13:02 ` Trilok Soni
2007-10-23 0:53 ` Tony Lindgren
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=47F4E1AF.5060509@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=linux-c-programming@vger.kernel.org \
/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 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.