mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Collins <ben.collins@ubuntu.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [ANNOUNCE] Ubuntu kernel tree
Date: Wed, 9 Nov 2005 06:12:16 -0800	[thread overview]
Message-ID: <20051109141216.GB30611@swissdisk.com> (raw)
In-Reply-To: <20051106202609.GA12481@elf.ucw.cz>

On Sun, Nov 06, 2005 at 09:26:09PM +0100, Pavel Machek wrote:
> Hi!
> 
> > Some people may have noticed the new git tree located at:
> > 
> > rsync.kernel.org:/pub/scm/linux/kernel/git/bcollins/ubuntu-2.6.git
> > 
> > This tree will directly reflect the Ubuntu Linux Kernel that is available
> > in our distribution (along with build system). First use of this kernel
> > tree is slated for Dapper Drake (Ubuntu 6.04), and will stay synced with
> > the just released 2.6.14(.y).
> > 
> > There are several reasons for making this repo available on kernel.org.
> > Primary reasons include a more open development model, better visibility
> > with the kernel developer community, and to make the kernel available to
> > other distro's who may want to base their kernel off of ours.
> 
> Heh, I'm interested. We were thinking about using git for internal
> suse kernel trees, but we thought it would not work, as we need more
> something like quilt. Do you really use git internally, or do you just
> export to it? If git is usable for distro develompent... that would be
> good news. 

Prior to this we were using baz (arch derivative), but all the patches
were still applied at build time.

We're giving git a go just to see. It's all being done right there, I push
directly to master.kernel.org (and also mirror it to a local machine where
ubuntu devs can make better use of it).

-- 
   Ben Collins <ben.collins@ubuntu.com>
   Developer
   Ubuntu Linux

  reply	other threads:[~2005-11-09 15:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-06  1:37 Ben Collins
2005-11-06 10:54 ` Jon Masters
2005-11-06 11:03 ` Rogério Brito
2005-11-06 14:48 ` Daniel Drake
2005-11-06 19:02   ` Jon Masters
2005-11-06 22:38   ` Alan Cox
2005-11-07 16:33     ` Daniel Drake
2005-11-07 17:08       ` Alan Cox
2005-11-07 17:05         ` Xavier Bestel
2005-11-07 17:23           ` Michael Alan Dorman
2005-11-07 17:32           ` Adrian Bunk
2005-11-09 14:09             ` Ben Collins
2005-11-06 20:26 ` Pavel Machek
2005-11-09 14:12   ` Ben Collins [this message]
2005-11-09 22:20     ` Greg KH
2005-11-06 20:36 ` Greg KH
2005-11-09 14:13   ` Ben Collins
2005-11-07 16:44 Xose Vazquez Perez

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=20051109141216.GB30611@swissdisk.com \
    --to=ben.collins@ubuntu.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®