Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: No branch
Date: Sun, 29 Feb 2004 17:12:00 -0000	[thread overview]
Message-ID: <20040229171239.GJ15749@nevyn.them.org> (raw)
In-Reply-To: <40415E02.9000908@gnu.org>

On Sat, Feb 28, 2004 at 10:35:30PM -0500, Andrew Cagney wrote:
> Given this sudden flood of patches, I've abandoned todays branch 
> attempt, I'll try again tomorrow, GMT
> 
> Daniel, can you please clear that patch backlog.

I have checked in the gdbserver and regcache patches.

I have plenty more, either waiting for approval or waiting on my drive
to be broken out, retested, and submitted.  There are also four more
targets I intend to test before release which I expect to be in equally
bad shape.  I will sit on them for a while.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-02-29 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29  3:35 Andrew Cagney
2004-02-29 17:12 ` Daniel Jacobowitz [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=20040229171239.GJ15749@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox