public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Hans-Peter Nilsson <hp@bitrange.com>, cgen@sources.redhat.com
Subject: Re: [RFA:] Fix for lsb0? in -gen-extract-word, take 2.
Date: Mon, 24 Jun 2002 21:06:00 -0000	[thread overview]
Message-ID: <15639.60410.566425.365304@casey.transmeta.com> (raw)
In-Reply-To: <20020624234746.A1432@redhat.com>

Frank Ch. Eigler writes:
 > Unfortunately, only "medium-weird" ports are on the sourceware
 > cgen repository, so it's possible that a change will break only
 > a port you don't (yet) have access to.

cgen shouldn't be held ransom be Redhat.
By that I mean if Redhat has proprietary ports it hasn't released yet
that's its problem, not the net's.

If a change doesn't break any existing net port (and diff'ing
the generated files before/after goes a long way to doing that (*)),
and the change is desirable, then the change should go in.
Let Redhat have "REDHAT LOCAL" mods if it needs.

Yes I know Redhat still has the copyright, but does it want to
play nice with the net and encourage progress and net contributions
or restrict it by saying "no you can't do that because it will break
one of our internal ports".

If the change is TRTTD, Redhat should welcome it and adapt.
If it can't right away, deal with it.  It's not like the folks
at Redhat don't have any experience dealing with local mods. :-)

(*) A script to do this would be a very useful addition.
[insert various caveats]   Someone want to write it?

  reply	other threads:[~2002-06-25  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 18:50 Hans-Peter Nilsson
2002-06-24 20:48 ` Frank Ch. Eigler
2002-06-24 21:06   ` Doug Evans [this message]
2002-06-25  3:20     ` Frank Ch. Eigler

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=15639.60410.566425.365304@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@redhat.com \
    --cc=hp@bitrange.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).