From: andrew may <acmay@acmay.homeip.net>
To: Matt Porter <mporter@mvista.com>
Cc: andrew may <acmay@acmay.homeip.net>,
Eugene Surovegin <ebs@innocent.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Status of 440GP port
Date: Tue, 2 Apr 2002 16:28:16 -0800 [thread overview]
Message-ID: <20020402162816.D5189@ecam.san.rr.com> (raw)
In-Reply-To: <20020402232048.GF20767@beef.az.mvista.com>
On Tue, Apr 02, 2002 at 04:20:48PM -0700, Matt Porter wrote:
>
> On Tue, Apr 02, 2002 at 02:54:00PM -0800, andrew may wrote:
> > On Tue, Apr 02, 2002 at 03:21:47PM -0700, Matt Porter wrote:
> > > On Tue, Apr 02, 2002 at 01:41:09PM -0800, andrew may wrote:
> > > > On Tue, Apr 02, 2002 at 02:18:45PM -0700, Matt Porter wrote:
> > > > >
> > > > > On Tue, Apr 02, 2002 at 11:46:12AM -0800, Eugene Surovegin wrote:
> > > >
> > > > So are you useing your own repository to track your development? It sure
> > > > doesn't seem like the 2_4_devel tree is a development tree anymore. And
...
> So I don't use the tool the way you do. That's the granularity I might
> normally use for local checkins, but we've never really had that kind
> of granularity on _devel pushes. It's not used that way.
Well that would be my point, that _devel tree is not used for direct
development.
> > I would sure not want to work for 4-5 weeks between pushes. I like to be
> > able to make dangerous changes to code knowing that I can always fall back
> > to a few day older version that sort-of worked.
>
> Local backups, .origs, local checkins. Again, different style of
> development. Luckily, nobody yet controls how develop on my own
> machine. 4-5 weeks is just a one time initial seed of a starting
> point.
So that would be the answer to my first question of what you are useing
to track your own development. You didn't answer it the first time around
it would seem like you were using the _devl tree as your source control
method. I don't even use bitkeeper and I could care less if you did or not,
but I asked what you were using.
> Those are the options. I'll make it available when it makes sense
> to open the floodgates of bug reports.
A bug report should never be written against a development tree. You can
always see a flood of problems on lkml, but most of them are just ignored
for being stupid user issues.
> I'm looking forward to having lots of eyeballs on it...this is not a
> new concept to me, thanks.
Well you seem to have the attitude that you are the only one that is
capable of working on things at the moment.
I would ask you to give some examples of people that are working on the Linux
kerenl that do 4-5 weeks of development without public review.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-03 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 19:46 Status of 440GP port Eugene Surovegin
2002-04-02 21:18 ` Matt Porter
2002-04-02 21:41 ` andrew may
2002-04-02 22:21 ` Matt Porter
2002-04-02 22:54 ` andrew may
2002-04-02 23:20 ` Matt Porter
2002-04-03 0:28 ` andrew may [this message]
2002-04-02 23:29 ` Frank Rowand
2002-04-03 0:08 ` Amit D. Chaudhary
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=20020402162816.D5189@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=ebs@innocent.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mporter@mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.