On Fri, Oct 30, 2009 at 11:58:19AM +0100, Stefan Reinauer wrote:
Both hold some weight. In practise v2 is already no longer v2. Until there are resources to start work on a new branch, let's just be version free!
Yes, I agree on version-free. svn revisions are our version and I do hope that we never will need or want a "rewrite from scratch" such as v3 was, but use gradual improvements instead. Even if we did a major rewrite that would likely be an extra repo again anyway.
(this moves all sudirectories of coreboot-v2 to trunk and wipes the coreboot-v2 directory as soon as it's empty. Then the directory hierarchy would be more similar to, e.g. flashrom)
If moving then I prefer this. Do the job properly when the knife is out anyway. :)
I think I agree.
I'm not so sure personally. Anyway, there are many issues to discuss before we start this massive amount of moving stuff, please leave time for at least 1-2 weeks discussion of whether it should be done, how it would be done best, and how users can recover their trees, what developers have to do to not lose work in their many trees etc. etc.
svn://coreboot.org/repos/trunk/coreboot-v2/{COPYING,Makefile,NEWS,README,documentation,src,targets} \ svn://coreboot.org/repos/trunk/
I also agree with Carl-Daniel that it would be nice to change "repos". Maybe to coreboot.org/coreboot/trunk/ ?
That's simple and I would like to see this, too.
Yep, that's fine I guess.
As Carl-Daniel noted, we should be moving coreboot-v1 out of the way. would branches/coreboot-v1 be an acceptable place?
No, I don't think so. branches and tags should contain branches of the same codebase, but v1 is a totally different tree. If you want to get rid of it in this repo, the best way is probably to move it to its own v1 repo (while keeping history intact, of course).
Uwe.