Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Strings and arrays without malloc
Date: Thu, 13 Mar 2008 20:47:00 -0000	[thread overview]
Message-ID: <m3r6ee1jtb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m363vq4ni7.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu\, 13 Mar 2008 10\:06\:24 -0600")

Tom> I only suggested git since I started with a clone of Volodya's
Tom> repository.  If you have something set up, I'm happy with that.
Tom> Otherwise, if you like, I'll look into hosting options a bit.

I decided to preserve history and make a public clone of Volodya's
repository.  Not knowing git very well, I'm sure I screwed something
up.  However, I can at least check it out using:

git clone http://git.gitorious.org/gdb-python/mainline.git
cd mainline
git checkout -b python origin/python

(If someone knows how to fix this to DTRT, I'm all ears.)

Anyway, this repository has Volodya's initial code, Daniel's
host-side-string patch, and all the Python stuff I've got so far.  If
you (anyone, not just you Thiago) are interested in helping out, and
you have an FSF assignment on file, I can set you up with write
access.

I assume that we can continue to use the gdb lists to discuss things.
If this bothers folks I guess we can set up a google group or something.

Tom


  reply	other threads:[~2008-03-13 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 16:14 Daniel Jacobowitz
2008-03-09 22:20 ` Eli Zaretskii
2008-03-11  6:58 ` Tom Tromey
2008-03-13  6:12   ` Tom Tromey
2008-03-13 14:16     ` Thiago Jung Bauermann
2008-03-13 14:54       ` Tom Tromey
2008-03-13 16:22         ` Thiago Jung Bauermann
2008-03-13 16:59           ` Tom Tromey
2008-03-13 20:47             ` Tom Tromey [this message]
2008-03-13 19:22 ` Joel Brobecker
2008-03-21 15:03   ` Daniel Jacobowitz

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=m3r6ee1jtb.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox