Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Grant Edwards <grante@visi.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: Hiro Sugawara <hsugawar@brocade.com>, gdb@sources.redhat.com
Subject: Re: dump memory to file
Date: Wed, 22 Aug 2001 11:25:00 -0000	[thread overview]
Message-ID: <1010822182455.ZM31473@ocotillo.lan> (raw)
In-Reply-To: <20010822125347.A32121@visi.com>

On Aug 22, 12:53pm, Grant Edwards wrote:

> > However, for such a change to be incorporated into GDB, the
> > author(s) of the change must have a copyright assignment in
> > place with the FSF. Sometimes it quite challenging to make sure
> > that all of the legal documents are signed by the right
> > people...
> 
> OK, let me see if I've got this: LynuxWorks can't not
> distribute the changes, and they can't prevent anybody else
> from distributing them, but the changes won't be incorporated
> into the official sources without a copyright assignment.

Right.

> I just went through the whole copyright assignment thing with
> my employer so I could donate some stuff to eCos.  It took
> years and cost thousands of lives.
> 
> Well... it did take almost a year.

I know.  I can tell some similar stories from personal experience.

In my opinion, there are many worthwhile changes that don't make it
into the mainline sources because the legal hoop jumping is so
difficult.  Many people are more than happy to send you their changes
and tell you (in email) that these changes may be incorporated into
the the sources, but they are absolutely not interested in obtaining
the legal documents and then pushing these documents through the
appropriate corporate channels to be signed by all the right people.
Frequently too, the corporate lawyers need to become involved and
when this happens, it can drag out the process almost interminably.

> Unless LynuxWorks is already set up to do stuff like that, it
> would be easier for me to just impliment it on my own.  I
> suppose it won't hurt to ask them -- I'm pretty sure I've got a
> business card from that Embedded Systems Conference...

It certainly won't hurt to ask, but, since you already have an
assignment in place, it will almost certainly be quicker to
reimplement this functionality yourself.

Kevin


  reply	other threads:[~2001-08-22 11:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 10:25 Hiro Sugawara
2001-08-22 10:31 ` Grant Edwards
2001-08-22 10:43   ` Kevin Buettner
2001-08-22 10:51     ` Grant Edwards
2001-08-22 11:25       ` Kevin Buettner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-22 11:18 Hiro Sugawara
2001-08-22 11:01 Hiro Sugawara
2001-08-22 11:10 ` Grant Edwards
2001-08-22  8:58 Grant Edwards
2001-08-22 10:18 ` Eli Zaretskii
2001-08-22 10:52 ` Kevin Buettner
2001-08-22 11:00   ` Daniel Jacobowitz
2001-08-22 12:00     ` Andrew Cagney
2001-08-22 11:02   ` Grant Edwards
2001-08-22 11:25   ` Per Bothner
2001-08-22 12:06     ` Kevin Buettner
2001-08-22 12:11     ` Andrew Cagney
2001-08-22 13:50   ` Jamie Guinan
2001-08-22 14:19     ` Grant Edwards

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=1010822182455.ZM31473@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=grante@visi.com \
    --cc=hsugawar@brocade.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