Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJBARROW@de.ibm.com
To: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sourceware.cygnus.com
Cc: BOAS@de.ibm.com
Subject: Re s390 gdb patches
Date: Tue, 19 Sep 2000 02:55:00 -0000	[thread overview]
Message-ID: <C125695F.00366D7C.00@d12mta09.de.ibm.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]

Hi Andrew,

As you already know but I probably phrased it badly
Boas has to post a letter to gnu.org handing over the "ownership" of the
sources to gnu.org.

The way I was planning on working this rather than having Boas fill out
multiple letters is that
he posts one letter when the patches get accepted by you all.

He also needs to post an md5 checksum to authenticate the patches ( I think
this is an IBM thing I saw no
mention of it on the release letter) for more info on md5 look at the
md5sum command.

If possible give me some feedback on the patches this morning as I'll be
out for the rest of the week.


D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen


Andrew Cagney <ac131313@cygnus.com> on 19.09.2000 07:01:37

Please respond to Andrew Cagney <ac131313@cygnus.com>

To:   Denis Joseph Barrow/Germany/Contr/IBM@IBMDE
cc:   Boas Betzler/Germany/IBM@IBMDE, Gregory Burke/Poughkeepsie/IBM@IBMUS,
      gdb-patches@sourceware.cygnus.com, Michael Snyder
      <msnyder@redhat.com>
Subject:  Re:




DJBARROW@de.ibm.com wrote:
>
> Hi,
> I forgot in the last note, let Boas & me know if the patches are accepted
> or rejected so that we can
> send the correct md5 checksums & the release letter.

Puzzled expression.

I'm pretty sure that parts of the changes will need more work (that is
without looking at them ;-).  This sort of thing needs to be done
incrementally.  It is simply a part of life.

What exactly do you mean when you refer to an md5 checksum and release
letter?  For this to work, you'll need to assign the changes and then
set up some sort of arangement where by you can continue to submit
patches.

I'm sorry but I'm confused.

     Andrew


> D.J. Barrow Linux for S/390 kernel developer
> eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
> Phone: +49-(0)7031-16-2583
> IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen




             reply	other threads:[~2000-09-19  2:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-19  2:55 DJBARROW [this message]
2001-08-23  7:14 re " Denis Joseph Barrow
2001-08-23  8:59 ` Andrew Cagney
2001-08-23  9:22 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=C125695F.00366D7C.00@d12mta09.de.ibm.com \
    --to=djbarrow@de.ibm.com \
    --cc=BOAS@de.ibm.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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