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

Re: Tracking vendor sources

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-03-24 03:48:27 CET

Kenneth P. Turvey wrote:
> Hash: SHA1
> I've pretty much decided that I'm going to have to start using a
> custom kernel under Ubuntu (Linux) for various reasons that I won't
> bother you with now. Since I'm going to have to use a custom kernel I
> don't see any point in not keeping up with developments in the stable
> version of the kernel and the various patches that I will need. This
> is where I'm a bit confused on how to use subversion to solve this
> problem.
> The issue is that I want to use multiple vendor branches to keep the
> sources in. That's where things start getting a bit messy. Some of
> the vendor sources are distributed as patches to specific versions of
> the kernel. I'm not sure how to organize this under subversion so I
> can update the patches as development proceeds along on them, merge
> them altogether with some version of the kernel (not necessarily the
> one they were distributed for) and maintain any of my own custom
> changes in trunk.
> Is there a standard way to solve this problem. I understand that the
> patch files can be checked in just as another file, but this just
> doesn't seem like the way to handle this. Shouldn't a patch really
> be applied on some branch in the repository?

I set up a "tagname" for the code from a vendor, then "tagname-vendor" for
the tarballs and patches from that vendor involved in creating the tag. You
can do the same with branches.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 24 03:49:25 2006

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.