[opensuse-kernel] expanded kernel-source (fate 309637)
Hi, here is the first prototype of https://features.opensuse.org/309637: http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git) It has the history of master, SLE11-SP1 and openSUSE-11.2 since their latest common commit. The scripts to generate this are at http://gitorious.org/mmarek-misc/expand-kernel-source There is still much to do, like handling of patches that do not apply, converting tags, adding merges with mainline / stable when the upstream version changes (to avoid useless huge diffs), converting commit id references in changelogs, etc. The goal is to have a repository that is automatically updated from kernel-source and is pullable. Right now, the repository can change at any time, so do not expect 'git pull' to work. On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 10.6.2010 11:50, Michal Marek wrote:
Hi,
here is the first prototype of https://features.opensuse.org/309637:
http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git)
Cut & paste error: The url of the kernel tree is git://gitorious.org/mmarek-misc/kernel-source-expanded.git Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thursday 2010-06-10 11:51, Michal Marek wrote:
On 10.6.2010 11:50, Michal Marek wrote:
Hi,
here is the first prototype of https://features.opensuse.org/309637:
http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git)
Cut & paste error: The url of the kernel tree is
git://gitorious.org/mmarek-misc/kernel-source-expanded.git
There's not much expanded stuff in there however. "Where is the kernel code?"-Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 21.6.2010 17:51, Jan Engelhardt wrote:
On Thursday 2010-06-10 11:51, Michal Marek wrote:
On 10.6.2010 11:50, Michal Marek wrote:
Hi,
here is the first prototype of https://features.opensuse.org/309637:
http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git) Cut & paste error: The url of the kernel tree is
git://gitorious.org/mmarek-misc/kernel-source-expanded.git
There's not much expanded stuff in there however.
What is the problem? $ git clone git://gitorious.org/mmarek-misc/kernel-source-expanded.git Initialized empty Git repository in /home/michal/kernel-source-expanded/.git/ remote: Counting objects: 1593717, done. remote: Compressing objects: 100% (254017/254017), done. remote: Total 1593717 (delta 1328422), reused 1592107 (delta 1326812) Receiving objects: 100% (1593717/1593717), 404.53 MiB | 310 KiB/s, done. Resolving deltas: 100% (1328422/1328422), done. Checking out files: 100% (32917/32917), done. $ cd kernel-source-expanded/ $ ls COPYING Makefile crypto/ init/ mm/ sound/ CREDITS README drivers/ ipc/ net/ tools/ Documentation/ REPORTING-BUGS firmware/ kdb/ samples/ usr/ Kbuild arch/ fs/ kernel/ scripts/ virt/ MAINTAINERS block/ include/ lib/ security/ $ git log -p commit a126791d610bbc47ba54ac2364a1fb87ebead57d Author: Michal Marek <mmarek@suse.cz> Date: Thu Jun 3 14:44:44 2010 +0200 Merge branch 'scripts' suse-commit: 0ac49b3b0494f89ded45d5056a7f82639c2f1eb5 ... Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Monday 2010-06-21 23:01, Michal Marek wrote:
here is the first prototype of https://features.opensuse.org/309637:
http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git) Cut & paste error: The url of the kernel tree is
git://gitorious.org/mmarek-misc/kernel-source-expanded.git
There's not much expanded stuff in there however.
What is the problem?
$ git clone git://gitorious.org/mmarek-misc/kernel-source-expanded.git Initialized empty Git repository in /home/michal/kernel-source-expanded/.git/ remote: Counting objects: 1593717, done. remote: Compressing objects: 100% (254017/254017), done. remote: Total 1593717 (delta 1328422), reused 1592107 (delta 1326812) Receiving objects: 100% (1593717/1593717), 404.53 MiB | 310 KiB/s, done. Resolving deltas: 100% (1328422/1328422), done. Checking out files: 100% (32917/32917), done.
git clone git://git.gitorious.org/mmarek-misc/expand-kernel-source Initialized empty Git repository in /dev/shm/expand-kernel-source/.git/ remote: Counting objects: 104, done. remote: Compressing objects: 100% (98/98), done. remote: Total 104 (delta 49), reused 0 (delta 0) Receiving objects: 100% (104/104), 20.93 KiB, done. Resolving deltas: 100% (49/49), done.
Oh ok. Unfortunate naming of repositories I figure. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu 10-06-10 11:50:05, Michal Marek wrote:
On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. I guess this is a matter of general policy so we should get some common concensus for that. For example for me it is sometimes convenient to commit several patches at once - think for example of some feature backport. You have several patches, they form one logical block. So you copy them into our repository, edit series.conf, and commit changes. Easy... If you had to do it patch-by-patch, the amount of boring work would be considerably higher. But I agree that logically unrelated patches should go into separate commits.
Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 15.6.2010 13:36, Jan Kara wrote:
On Thu 10-06-10 11:50:05, Michal Marek wrote:
On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. I guess this is a matter of general policy so we should get some common concensus for that. For example for me it is sometimes convenient to commit several patches at once - think for example of some feature backport. You have several patches, they form one logical block. So you copy them into our repository, edit series.conf, and commit changes. Easy... If you had to do it patch-by-patch, the amount of boring work would be considerably higher.
I see. Would some 'scripts/addpatch <parent> <patch1> <patch2>...', that would automatically add and commit each patch, help here? Thanks, Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue 15-06-10 13:50:17, Michal Marek wrote:
On 15.6.2010 13:36, Jan Kara wrote:
On Thu 10-06-10 11:50:05, Michal Marek wrote:
On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. I guess this is a matter of general policy so we should get some common concensus for that. For example for me it is sometimes convenient to commit several patches at once - think for example of some feature backport. You have several patches, they form one logical block. So you copy them into our repository, edit series.conf, and commit changes. Easy... If you had to do it patch-by-patch, the amount of boring work would be considerably higher.
I see. Would some 'scripts/addpatch <parent> <patch1> <patch2>...', that would automatically add and commit each patch, help here? It would be certainly fine with me.
Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 15.6.2010 15:38, Jan Kara wrote:
On Tue 15-06-10 13:50:17, Michal Marek wrote:
On 15.6.2010 13:36, Jan Kara wrote:
On Thu 10-06-10 11:50:05, Michal Marek wrote:
On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. I guess this is a matter of general policy so we should get some common concensus for that. For example for me it is sometimes convenient to commit several patches at once - think for example of some feature backport. You have several patches, they form one logical block. So you copy them into our repository, edit series.conf, and commit changes. Easy... If you had to do it patch-by-patch, the amount of boring work would be considerably higher.
I see. Would some 'scripts/addpatch <parent> <patch1> <patch2>...', that would automatically add and commit each patch, help here? It would be certainly fine with me.
This is now implemented in the new scripts/log, just call scripts/log and it will split the commits for you. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 10.6.2010 11:50, Michal Marek wrote:
Hi,
here is the first prototype of https://features.opensuse.org/309637:
http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git)
It has the history of master, SLE11-SP1 and openSUSE-11.2 since their latest common commit. The scripts to generate this are at
http://gitorious.org/mmarek-misc/expand-kernel-source
There is still much to do, like handling of patches that do not apply, converting tags, adding merges with mainline / stable when the upstream version changes (to avoid useless huge diffs), converting commit id references in changelogs, etc. The goal is to have a repository that is automatically updated from kernel-source and is pullable. Right now, the repository can change at any time, so do not expect 'git pull' to work.
I just rebased (*) the repository with a new version. The main improvement is that each "Update to 2.6.xx" commit is now a merge with the respective mainline version, so that you see the changes introduced by individual upstream commits directly (as opposed to those 30+MB "Updated to 2.6.xx-rc1" diffs). Could you please have a look at the repository and tell me if you're missing anythig or if something looks like a bug? I still have a few things in my TODO, but I'd like to have a pullable and automatically updated repository soon. This is what I'm planning to implement: * Convert tags * Convert references to commit ids in changelog entries (as in "This reverts commit 1234567889") * Reduce the number of broken trees as much as possible (there are some patches that only apply with certain version of patch(1)!) * Somehow solve the arch- and flavor-specific patches we still have in SLES9 (*) If you want to update an existing clone, do this: $ git fetch $ git checkout master $ git reset --hard origin/master and the same for SLE11-SP1 and openSUSE-11.2 have fun, Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (3)
-
Jan Engelhardt -
Jan Kara -
Michal Marek