[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 20:30:11 CEST

> Florian Weimer <fw@deneb.enyo.de> [2004-04-04 19:36]:
> Lukas Ruf wrote:
> > What I would like to have is something like a mapping of a file into
> > another tree. In this case, I would like to work on files in trunk
> > but have them 'mapped' into several other trees. This would imply
> > that all changes I would make to a file found in a branch were
> > immediately reflected in the trunk.
> I have worked with such a development environment (with immediate
> updates from trunk to branches, unless the file was copied to the
> branch and modified). It's extremely confusing.

ok, I see. Thanks for the discussion. I think I will follow your


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 20:30:50 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.