On Thu, Jul 12, 2007 at 11:08:20AM +0200, Stefan Reinauer wrote:
- Uwe Hermann uwe@hermann-uwe.de [070711 22:24]:
OK, not really a patch, but I think we can move lar into the global util/ directory and suck it into v3 via svn:externals.
That's a first step to make it independent of v3 (and to allow Jordan to use it in buildrom).
I'm waiting for comments or ACKs before doing this, though.
Will this drop the history? If so, strong NACK.
Ouch. I was about to say "yes, history is preserved", but I forgot that v3 is a _different_ repository at the moment! So no, we cannot just 'svn mv' lar easily (which is one of the many reasons why I object to different repos for our code).
You'd have to dump the v3 repository, and import it into the v2 repository (which I think we should do anyway) -- there are some tutorials on how to do that while preserving the history.
This has to be done by the admin (probably needs root access), and can _not_ be done by anybody with svn commit access (not if you want to preserve history, that is).
_Then_, it's a simple 'svn mv' to move lar into the global util/.
Oh, another possibility would be to just commit the current v3 code into the v2 repository (and dropping the history!) like this:
- trunk - LinuxBIOSv1 - LinuxBIOSv2 - LinuxBIOSv3 <----- commit v3 right into that directory - util
Yes, we would _not_ have the history in that new LinuxBIOSv3 directory. But maybe it's still an option, because we could leave the current extra v3 repo around as an "early development testbed" repository, so people can lookup the history there.
Comments? I'm fine with either of the two approaches.
It is NOT a generic utility yet.
Yep, but patches are floating in to make it generic :)
Uwe.