ext Greg KH wrote:
On Fri, May 28, 2010 at 04:15:29PM +0300, Roger Quadros wrote:
Hi,
ext Greg KH wrote:
On Thu, May 27, 2010 at 07:27:40PM +0300, Ameya Palande wrote:
Hi Greg,
On Thu, 2010-05-27 at 16:51 +0200, ext Greg KH wrote:
On Thu, May 27, 2010 at 05:30:46PM +0300, Roger Quadros wrote:
hi,
The Meego N900 kernel can be found at the following location
http://gitorious.org/meego-device-adaptation/n900_kernel-devel
OR
git://gitorious.org/meego-device-adaptation/n900_kernel-devel.git
'MeeGo-1.0' branch is synced with the N900 kernel in the 1.0 release.
Why is this just not part of the main meego kernel tree? Why a separate
branch?
confused,
greg k-h
Are you talking about "meego-os-base/kernel-source"?
Yes.
Doing kernel development using kernel-source repo IMO is difficult.
Why?
I guess main intention of that repo is packaging of patches on top of
MeeGo kernel.
That's how kernel development works.
I guess Roger's intention is to create a git repo for kernel
development. Anyone can just clone this, create a patch and send it to
meego-dev.
The only purpose was to create a visible tree with what is in
meego-1.0 release for n900.
Then how are you going to handle things that change as the release moves
forward, given that you agree with my statement:
If that is so, then it should be specified. Note that using an expanded
kernel tree to do development like this is _very_ difficult and you will
get burned very easy. It is not recommended that you do this, and it is
recommended that you handle development like the main MeeGo kernel tree
does it.
Agreed.
This implies that this tree is a dead-end. What happens to it when the
next stable kernel update (well, the last one, the tree is a bit behind)
is applied to the main kernel repo? You will have to rebase this whole
tree then, right? That breaks anyone who might have cloned it.
Agreed.
I will remove this tree and have a separate git tree for N900 related kernel
development which is not specific to Meego but allows N900 users to have a
working tree for N900.
regards,
-roger
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
