Since It's clear that with more peoples working on it, there is a need of
synchro.
Here's what I'm proposing :
I'll a tree :
bk://bkbits.246tNt.com/linux-mpc52xx-devel
This tree would contain all the latest code to be tested by
others. Just send patch to the ml and cc me, I'll put them in this
tree. Once every one is happy with it (or part of it), I'll take
care of pushing it upstream.
Note that since all current work with bestcomm is based on
non-GPL code, It won't be in until Dale send me the version he's
working on (based on latest code).
To avoid duplicate work, you can post here what you're doing, I'll try
to keep
http://www.246tNt.com/mpc52xx/state-devel.txt up-to-date with who's doing what.
The point is to centralize the testing code and having a 'single' contact
to merge the work upstream to ease the work of upstream maintainers.
This tree is being setup right now, please allow a few hours ;)
Comments, suggestions are of course welcome.
Sylvain
Andrey Volkov wrote:
Hello David,
Tuesday, August 24, 2004, 12:54:46 PM, you wrote:
quoted
On Tue, 2004-08-24 at 12:07 +0400, Andrey Volkov wrote:
quoted
Terrible, may be its time to create special project for MPC5200 (if it
doesn't exist in somewhere in I-net)? First intention - sourceforge.
Comments/suggestions?
quoted
Don't start a new project. Just put your changes into the official 2.6
tree.
quoted
The goal of _all_ external trees should be to make themselves obsolete
by getting all changes to Linus as quickly as possible. Why shoot
yourself in the foot?
Indeed, BUT:
1) IMHO mail list better approach for
along developer <-> maintainer/many tester
scheme of development. Cvs/bk will be better for team work isn't it?
2) So somewhere must exist place for coordination of job, 'cause
I see as minimum 5 person doing SAME work (terrible).
3) And I wish have common place for experiments and testing. AFAIK, stable
kernel is not appropriate for it. (If I wrong - why exist -mm -ac
etc branches? :)
--
Best regards,
Andrey Volkov
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/