linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: Andre Haupt <andre@bitwigglers.org>
Cc: Yegor Yefremov <yegor_sub1@visionsystems.de>,
	linux-c-programming@vger.kernel.org
Subject: Re: Git tags
Date: Thu, 03 Apr 2008 16:40:06 +0200	[thread overview]
Message-ID: <47F4EC46.5030307@visionsystems.de> (raw)
In-Reply-To: <20080403143250.GA16034@ahaupt-debian-vm.localdomain>

Dear Andre,

thank you for your answer. Yes. I have made some changes to the kernel 
sources. Is it really so, that if I make some changes Makefile or some 
other script notices this fact and adds "dirty" to the kernel version 
string?

Best regards,
Yegor

Andre Haupt wrote:
> On Thu, Apr 03, 2008 at 03:54:55PM +0200, Yegor Yefremov wrote:
>   
>> 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.
>>     
>
> Do you have uncommited local changes in your git tree?
>
> Best regards,
>
> Andre
>
>   


  reply	other threads:[~2008-04-03 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 13:54 Git tags Yegor Yefremov
2008-04-03 14:32 ` Andre Haupt
2008-04-03 14:40   ` Yegor Yefremov [this message]
2008-04-03 14:47     ` Andre Haupt
2008-04-03 14:55       ` Andre Haupt

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=47F4EC46.5030307@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --cc=andre@bitwigglers.org \
    --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 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).