Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] Moving to GPLv3 ... (part 0/???)
Date: Tue, 21 Aug 2007 13:43:00 -0000	[thread overview]
Message-ID: <20070821134333.GD25612@caradoc.them.org> (raw)
In-Reply-To: <20070818013915.GB24165@adacore.com>

On Fri, Aug 17, 2007 at 06:39:15PM -0700, Joel Brobecker wrote:
> I'll be traveling all of next week, but I would still like to have
> these checked in by then. I should be able to find some time for
> the commits.
> 
> Let me know if I missed any file!

I've looked at all the patches that Michael hadn't already, somewhat
briefly.  They all look fine to commit as far as I'm concerned; I
think you should go ahead.  The diff for the .exp files was corrupted
in transit but I'm sure you did it right :-)

I don't know if there are any additional files in sim which we should
be updating but I suspect there are.  Anyway, this gets us 99% of the
way there.

Does the documentation need an update?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-08-21 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18  1:35 Joel Brobecker
2007-08-21 13:43 ` Daniel Jacobowitz [this message]
2007-08-23 17:53   ` Joel Brobecker

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=20070821134333.GD25612@caradoc.them.org \
    --to=drow@false.org \
    --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