Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: binutils@sourceware.org, gdb@sourceware.org, gcc@gnu.org,
		DJ Delorie <dj@redhat.com>
Subject: toplevel *again* out of sync
Date: Sat, 02 Oct 2010 08:47:00 -0000	[thread overview]
Message-ID: <AANLkTi=OyoPFcw7-0uYoZNjX7SjtHya=hP8nruxKwQic@mail.gmail.com> (raw)

I hate to say this when I don't have the time to fix it myself, but
toplevel of gcc and src is once more out of sync, and this is bad.

I think that we should apply a *very* strict policy of not approving
toplevel patches unless the toplevel files are in sync.

Thanks in advance to anyone that "volunteers" to fix things...

Paolo


             reply	other threads:[~2010-10-02  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02  8:47 Paolo Bonzini [this message]
2010-10-02  9:18 ` Ralf Wildenhues
2010-10-02 12:40   ` Ralf Wildenhues
2010-10-02 14:03     ` Paolo Bonzini
2010-10-03  7:59       ` DJ Delorie
2010-10-04  8:44     ` Naveen H. S
2010-10-07 19:27       ` Ralf Wildenhues

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='AANLkTi=OyoPFcw7-0uYoZNjX7SjtHya=hP8nruxKwQic@mail.gmail.com' \
    --to=bonzini@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --cc=gcc@gnu.org \
    --cc=gdb@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