[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best Practice To Track Linux Kernel Changes

From: Lukas Ruf <ruf_at_rawip.org>
Date: 2004-04-04 17:00:42 CEST

> Florian Weimer <fw@deneb.enyo.de> [2004-04-04 11:16]:
> Lukas Ruf wrote:
> > One (next) issue I do not know how to handle with subversion is:
> > - I am working on several extensions to the Linux kernel of which I
> > managed the source codes to keep running with latest 2.4 and 2.6 kernels.
> > - However, I need to stay up-to-date with the kernel core-development,
> > i.e. whenever a new kernel is released, I must important that kernel
> > into the repository and apply all the patches.
> Do you need BK changeset granularity in your Subversion repository?

no. I simply need an "easy" way to port my development to the latest
stable kernels.

What I would like to have is:
- my code resides in the trunk (approx. 20 files)
- the whole kernel in the repository as a branch to my code
- whenever a new kernel appears I would like to simply switch the
  kernel code beneath my code.

Does something like this make sense? Or are there better approaches?



Lukas Ruf           | Wanna know anything about raw |
<http://www.lpr.ch> | IP? -> <http://www.rawip.org> |
eMail Style Guide: <http://www.rawip.org/style.html>|
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 4 17:01:10 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.