From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: ALT Linux kernel packages development <devel-kernel@lists.altlinux.org>
Subject: Re: [d-kernel] i: kernel-source-2.6.x howto
Date: Tue, 22 Dec 2009 14:35:35 +0200
Message-ID: <cc557aab0912220435u7574685as6b5bfc72166f55@mail.gmail.com> (raw)
In-Reply-To: <20091222122114.GA7625@wo.int.altlinux.org>
2009/12/22 Dmitry V. Levin <ldv@altlinux.org>:
> On Tue, Dec 22, 2009 at 01:31:18AM +0200, Kirill A. Shutemov wrote:
>> 2009/12/22 Dmitry V. Levin <ldv@altlinux.org>:
>> > On Mon, Dec 21, 2009 at 11:35:12PM +0200, Michael Shigorin wrote:
>> >> On Mon, Dec 21, 2009 at 10:49:35PM +0200, I wrote:
>> >> > > Кто возьмётся документировать создание новых kernel-source-2.6.x?
>> >> > Понял, приступаю.
>> >>
>> >> Просьба посмотреть: http://www.altlinux.org/Kernel/Source
>> >
>> > Судя по выводу
>> > $ git log v2.6.30..kernel-source-2.6.30-1.0.0-alt1
>> > есть традиция наследовать новые kernel-source от старых.
>> >
>> > Т.е. нужно заменить git init клонированием
>> > git://git.altlinux.org/gears/k/kernel-source-2.6.30.git
>> >
>> > Ну и дальше упростить процедуру.
>>
>> А имеют ли смысл kernel-source-* при сборке из git? Я так понимаю, что они
>> задумывались для минимизации трафика при заливке нового релиза ядра.
>
> Есть: у нас более одного пакета собираются из одного kernel-source.
Т.е. экономия на объёме SRPM'ов?
next prev parent reply other threads:[~2009-12-22 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 21:40 [d-kernel] q: " Michael Shigorin
2009-12-21 20:49 ` Michael Shigorin
2009-12-21 21:35 ` [d-kernel] i: " Michael Shigorin
2009-12-21 23:00 ` Dmitry V. Levin
2009-12-21 23:31 ` Kirill A. Shutemov
2009-12-22 12:21 ` Dmitry V. Levin
2009-12-22 12:35 ` Kirill A. Shutemov [this message]
2009-12-22 18:39 ` Dmitry V. Levin
2009-12-23 18:11 ` Michael Shigorin
2009-12-23 18:24 ` Igor Zubkov
2009-12-23 18:33 ` Michael Shigorin
2009-12-23 19:18 ` Igor Zubkov
2009-12-23 21:22 ` Michael Shigorin
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=cc557aab0912220435u7574685as6b5bfc72166f55@mail.gmail.com \
--to=kirill@shutemov.name \
--cc=devel-kernel@lists.altlinux.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
ALT Linux kernel packages development
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
public-inbox-index devel-kernel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git