Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: Adam Fedor <fedor@doc.com>, Daniel Jacobowitz <drow@mvista.com>,
	gdb-patches@sources.redhat.com,
	weigand@informatik.uni-erlangen.de
Subject: Re: [PATCH] Fix some 64-bit Objective-C bugs
Date: Mon, 19 Jan 2004 19:52:00 -0000	[thread overview]
Message-ID: <400C3586.1060104@gnu.org> (raw)
In-Reply-To: <OF2F94C177.61BC23BD-ONC1256E20.0068EB5B@de.ibm.com>

> Andrew Cagney wrote:
> 
> 
>>Yes, better safe than sorry.  Ulrich, can IBM do the paperwork for all
>>the stuff that's approved (this would leave just frame cleanup).
> 
> 
> OK, I've respun the s390 backend patches to adapt them to the latest
> changes and also to fix everything reported by ARI (-Wari only, not -Wall).
> I'll post the latest version shortly.

Thanks.

> I'll then immediately start the legal process for
>   - the main backend patches (part 1 .. 4)
>   - the bi-arch patch
>   - the ObjC patch
> 
> (The Java patch was incorrect, and the DWARF-2 patch still awaits some
> common code changes.)
> 
> I hope we can get this through in time for gdb 6.1 ...
> 
> What's the policy for the branch?  In case the paperwork is still not
> ready at the time the branch is created, can we still get the patches
> in afterwards (after all, the contents are already approved ...)?

Things are a lot more flexible than GCC.  In the past we've ended up 
with s390 specific patches being committed to the branch.  Also I've 
seen your assignment lawyers in action - they move much faster than you 
might think.

Main thing is to try and get the changes you depend on sorted out before 
the branch.

Andrew


  reply	other threads:[~2004-01-19 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 19:27 Ulrich Weigand
2004-01-19 19:52 ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-20 17:42 Ulrich Weigand
     [not found] <E5F2FFE55E362144876F14CB0AEE713901EB72C5@exchange1.urp.doc.com>
2003-12-05 17:45 ` Adam Fedor
2004-01-19 16:33   ` Daniel Jacobowitz
2004-01-19 17:31     ` Adam Fedor
2004-01-19 18:19       ` Andrew Cagney
2004-01-19 18:20         ` Daniel Jacobowitz
2003-12-04 20:10 Ulrich Weigand

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=400C3586.1060104@gnu.org \
    --to=cagney@gnu.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=drow@mvista.com \
    --cc=fedor@doc.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=weigand@informatik.uni-erlangen.de \
    /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