public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: SuperH patch contributions
Date: Tue, 21 Sep 2004 13:02:00 -0000	[thread overview]
Message-ID: <20040921130238.GB10074@nevyn.them.org> (raw)
In-Reply-To: <200409211030.i8LAU8O29106@chloe.uk.w2k.superh.com>

On Tue, Sep 21, 2004 at 11:30:08AM +0100, Joern Rennecke wrote:
> > I'd recommend creating a branch so that you can both post and commit the 
> > changes.  Good luck!
> 
> I had an accident, an now there is unfortunately not enough time left
> to do things nicely.  I want to focus now on getting all the patches
> covered, and we can sort out later what part of it can be integrated
> and how.
> 
> I got a 48 MB gzipped tar file of a sh64 gdb + simulator build.
> Uuencoded this is 66 MB.
> This is based on a March 2002 snapshot and a number of RedHat patches.
> I did mostly patches to the simulator to make it simulate the right thing.
> Some of the configury bits (which I didn't wrote) didn't work quite right
> (or maybe I was missing some undocumented incantation), so I had to
> patch some of the post-configuration files; this is why I included all
> the build files in the tarball and it is so large.
> It is too large for tha mailing list - or should I split it up into twenty
> messages?  What is the preferred way to submit things that large?
> Note, there is no time left to identify the post-configuration mods or
> do patch review before I leave SuperH.  The objective now is to make these
> tools available, and to get the copyright assignment to cover them (which
> depends on submitting the code).

Please don't send it to the mailing list.  I believe the last time we
needed to do this we made some space on sources.redhat.com for it, but
I don't know where...

-- 
Daniel Jacobowitz

  reply	other threads:[~2004-09-21 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 15:50 Joern Rennecke
2004-09-17 18:02 ` Andrew Cagney
2004-09-21 10:33   ` Joern Rennecke
2004-09-21 13:02     ` Daniel Jacobowitz [this message]
2004-09-22 16:29       ` Andrew Cagney

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=20040921130238.GB10074@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=joern.rennecke@superh.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).