Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Readline 5.1 import
Date: Mon, 10 Apr 2006 19:04:00 -0000	[thread overview]
Message-ID: <uzmit45ia.fsf@gnu.org> (raw)
In-Reply-To: <20060410180030.GA29115@nevyn.them.org> (message from Daniel 	Jacobowitz on Mon, 10 Apr 2006 14:00:30 -0400)

> Date: Mon, 10 Apr 2006 14:00:30 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> I've done my best to preserve every local change.  The local changes are
> mainly for Cygwin, DJGPP, and MinGW32; I tested GNU/Linux, and did manual
> testing on both Cygwin and MinGW32.  My last attempt to build a DJGPP GDB
> took all day and failed horribly due to GCC bugs, so I'm afraid I can't
> test the __MSDOS__ bits.  But they're pretty straightforward and I did
> preserve all the local ones.

The MSDOS stuff is okay with me, assuming (as I understand from your
description) that all of the local changes were copied 1:1.

The documentation-related changes due to renaming of files are also
approved.

Thanks.


      parent reply	other threads:[~2006-04-10 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 18:00 Daniel Jacobowitz
2006-04-10 18:30 ` Elena Zannoni
2006-04-10 18:40   ` Daniel Jacobowitz
2006-04-10 18:54     ` Elena Zannoni
2006-04-10 18:57       ` Daniel Jacobowitz
2006-04-20 17:32         ` Daniel Jacobowitz
2006-04-20 20:43           ` Elena Zannoni
2006-04-21  1:16             ` Jim Blandy
2006-04-21 13:25               ` Elena Zannoni
2006-04-24 22:10             ` Daniel Jacobowitz
2006-05-01 13:56               ` Daniel Jacobowitz
2006-05-05 18:26                 ` Daniel Jacobowitz
2006-04-10 19:04 ` Eli Zaretskii [this message]

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=uzmit45ia.fsf@gnu.org \
    --to=eliz@gnu.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