Re: [ANNOUNCE] 2.6.33-rc8-rt1

GeunSik Lim
2010-02-24T21:54:11Z

On Thu, Feb 25, 2010 at 2:52 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Thu, 25 Feb 2010, GeunSik Lim wrote:
>> On Thu, Feb 25, 2010 at 12:09 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> >> So, I tried linux-2.6.33-rc8-rt1 based on tip/rt/head as you explained.
>> >>
>> >> Git development branch:
>> >>   git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head
>> > What's the sha1 of the head commit ?
>> > Thanks,
>> >        tglx
>> >
>> Dear Thoomas,
>>
>> Below was the  recent commit number  when I typed "git clone" command.
>>
>> commit ed0799048b4a38ffb6e33755ba5e6b5dfa9a24d2
>> Author: Thomas Gleixner <tglx@linutronix.de>
>> Date:   Sun Feb 21 23:14:28 2010 +0100
>>
>>     v2.6.33-rt1
>
> So you cloned the rt/2.6.33 branch of tip. rt/head does not have
> release numbers. The version in the Makefile is simply
> 2.6.33-rc8-rt. rt/head is where development happens. When stuff seems
> stable I update rt/2.6.xx and bump the -rt version and tag it.
Thank you for explanation of the rt/*** branch meaning. :)
Currently, I am using the rt/2.6.33 branch
with "git checkout -b v2.6.33-rc8-rt2 v2.6.33-rc8-rt2" command.

[invain@localhost 2.6.33]$ git branch
master
v2.6.33-rc8-rt1
* v2.6.33-rc8-rt2
[invain@localhost 2.6.33]$ pwd
/opt/rt/2.6.33

As I reported finally now is normal with -rc8-rt2.
* Booting result of linux-2.6.33-rc8-rt2 on Q9400 PC. --> Passed.
http://picasaweb.google.com/leemgs/LinuxRelatedScreenshot#5441865625183643634
>
> Thanks,
>
>        tglx

--
Regards,
GeunSik Lim ( Samsung Electronics )
Blog : http://blog.naver.com/invain/
e-Mail: geunsik.lim@samsung.com
leemgs@gmail.com , leemgs1@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html