From: Andrey Volkov <avolkov@varma-el•com>
To: David Woodhouse <dwmw2@infradead•org>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re[2]: [RFC] Re: BestComm and fec
Date: Tue, 24 Aug 2004 14:52:07 +0400 [thread overview]
Message-ID: <16210643353.20040824145207@varma-el.com> (raw)
In-Reply-To: <1093337686.3777.755.camel@imladris.demon.co.uk>
Hello David,
Tuesday, August 24, 2004, 12:54:46 PM, you wrote:
> On Tue, 2004-08-24 at 12:07 +0400, Andrey Volkov wrote:
>> 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?
> Don't start a new project. Just put your changes into the official 2.6
> tree.
> 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/
next prev parent reply other threads:[~2004-08-24 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <412A4B69.7000305@246tNt.com>
2004-08-24 8:07 ` [RFC] Re: BestComm and fec Andrey Volkov
2004-08-24 8:45 ` Sylvain Munaut
2004-08-24 8:54 ` David Woodhouse
2004-08-24 10:52 ` Andrey Volkov [this message]
2004-08-24 16:17 ` [RFC] MPC5200 dev (was Re: [RFC] Re: BestComm and fec) Sylvain Munaut
2004-08-24 16:51 ` Andrey Volkov
2004-08-24 16:10 ` [RFC] Re: BestComm and fec Dale Farnsworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16210643353.20040824145207@varma-el.com \
--to=avolkov@varma-el$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox