From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Matt Mackall <mpm@selenic.com>, Pavel Machek <pavel@suse.cz>,
akpm@osdl.org, george@mvista.com, Andi Kleen <ak@suse.de>,
jim.houston@comcast.net,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BitKeeper repo for KGDB
Date: Wed, 11 Feb 2004 20:05:13 +0530 [thread overview]
Message-ID: <200402112005.13624.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040210192649.GM5219@smtp.west.cox.net>
OOPS!
I started downloading your changes from bitkeeper web interface and didn't
finish that. We have got again out of sync.
I have setup a cvs repository in the meantime. More info at
http://kgdb.sourceforge.net/cvs.html
You can add yourself to kgdb project as a developer. Then you'll be able to
checkin changes yourself.
Thanks.
-Amit
On Wednesday 11 Feb 2004 12:56 am, Tom Rini wrote:
> On Tue, Feb 10, 2004 at 01:57:39PM +0530, Amit S. Kale wrote:
> > Tom,
> > Can you please post diffs wrt. 2.6.x kernels for the bitkeeper challanged
> > (me :)?
>
> I appologize for not getting to this sooner, but I've been doing a lot
> of cleanups and such to the code (and not being as well versed in the
> gdb protocol as I'd have like to been, spending some time looking into
> user-error type bugs). But I'm now at the point where I'm much happier
> with how KGDB works wrt breaking in, resuming sessions, etc, so I'm
> going to start double checking kgdboe again and hopefully checkin, and
> then break out for Andrew all of the stuff I've got. The following is
> a patch against what I've pushed last (debug bits and all):
next prev parent reply other threads:[~2004-02-11 14:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 18:40 BitKeeper repo for KGDB Tom Rini
2004-01-27 19:31 ` Sam Ravnborg
2004-01-27 19:46 ` Dave Jones
2004-01-27 20:07 ` Chris Wright
2004-01-27 21:02 ` Tom Rini
2004-01-28 9:50 ` Dave Jones
2004-01-28 16:51 ` Pavel Machek
2004-01-28 17:05 ` Tom Rini
2004-01-28 17:44 ` Pavel Machek
2004-01-28 17:56 ` Tom Rini
2004-01-28 18:04 ` Pavel Machek
2004-02-06 22:35 ` Tom Rini
2004-02-06 22:55 ` Pavel Machek
2004-02-06 23:02 ` Tom Rini
2004-02-09 1:29 ` Matt Mackall
2004-02-09 15:50 ` Tom Rini
2004-02-09 17:38 ` Matt Mackall
2004-02-10 7:57 ` Amit S. Kale
2004-02-10 8:27 ` Amit S. Kale
2004-02-10 19:26 ` Tom Rini
2004-02-11 14:35 ` Amit S. Kale [this message]
2004-02-10 8:46 ` Dave Jones
2004-02-10 19:22 ` Tom Rini
2004-02-10 19:23 ` Dave Jones
2004-01-30 18:18 ` Tom Rini
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=200402112005.13624.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=jim.houston@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@suse.cz \
--cc=trini@kernel.crashing.org \
/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.