Hi Hans, On Mon, 02 Apr 2007 10:17:41 +0200, Hans de Goede wrote: > I've been really busy lately with Fedora related "work", but I hope to find the > time soon to start working on the dyn chip support. Most of the code is already > tehre for the 2.x branch (written by my students). ANd my initial testing was good. > > This leads me to the following questions: > 1) What cmdline magic must I pass to svn to get the 3.x branch when checking > out? svn checkout http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0 > 2) Do I need any cmdline magic to make sure a commit goes to the 3.x branch? > (I've bad experiences with this with CVS, where a commit would go to the > default branch even though I checkout another) I've never done that, so I can't say for sure, but I think svn will remember what branch you checked out from and you don't need to add any parameter. Mark, can you please confirm this? > 3) Is it ok for me to just start committing this, or should I post it for > review here first? I am usually committing directly, except when I am not sure myself that this is the right thing to do, in which case I post on the list first, and then sometimes commit the change, sometimes not. So it's up to you, for changes you are sure of or that have already been discussed, just commit them, and use the list if you think something needs to be discussed first. Remember, the whole idea of a separate 3.0.0 branch is that you can put all your changes there quickly. Before you start really working on the 3.0.0 branch, we should sync it with the current trunk. Mark created the 3.0.0 branch quite some time ago, many fixes have gone into trunk since then, and I would hate to lose them. I don't know how this is done though. Mark, can you please take care of it? Maybe just kill the branch and recreate it? I also don't know how we are going to handle the later trunk changes, once 3.0.0 development is in progress. Some changes won't apply to the 3.0.0 branch (e.g. adding support for a new chip in libsensors) but many will. Once real work starts on this branch, it should be documented on our Download page how to get the code, if we want testers. It would also be convenient to have nightly snapshots as we do for the trunk version. Axel, can this be done? Thanks, -- Jean Delvare