Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sources.redhat.com
Subject: Re: GDB 6.5 branch on Sun May 14th
Date: Sun, 14 May 2006 16:03:00 -0000	[thread overview]
Message-ID: <20060514150621.GA29251@nevyn.them.org> (raw)
In-Reply-To: <20060514065732.GC6718@adacore.com>

On Sat, May 13, 2006 at 11:57:32PM -0700, Joel Brobecker wrote:
> >  > Now that the last couple of patches I thought were important enough to
> >  > delay 6.5 are in, I was thinking that maybe tomorrow would be a good
> >  > day to use as the start of the 6.5 branch. Any better suggestion?
> > 
> > Could I sneak in the change to -var-set-format that I submitted earlier?
> > (reproduced below).  There must be a chance that Emacs 22 will be released
> > before the GDB release after 6.5, and then I'll be up and running.
> 
> I am not opposed, but remember that you can always port this change
> to the branch if the patch is deemed safe enough but is committed
> too late.

Yes, that's a better idea.  Nick, I will respond to your questions
when I have another spare day to review GDB patches, but please
remember that I objected to the patch; some of your responses to not
make sense to me.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-14 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14  6:57 Joel Brobecker
2006-05-14  7:33 ` Nick Roberts
2006-05-14 10:41   ` Joel Brobecker
2006-05-14 16:03     ` Daniel Jacobowitz [this message]
2006-05-14 22:38       ` Nick Roberts
2006-05-14 22:44         ` Daniel Jacobowitz
2006-05-14 21:29   ` Eli Zaretskii
2006-05-14 16:40 ` Daniel Jacobowitz
2006-08-22  9:51 Nick Roberts

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=20060514150621.GA29251@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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