public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: John Reiser <jreiser@BitWagon.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [PATCH] Re: ld: orthogonal functionality?
Date: Wed, 19 Sep 2001 10:53:00 -0000	[thread overview]
Message-ID: <3BA8DC06.7F513F01@BitWagon.com> (raw)
In-Reply-To: <20010919091308.E30455@lucon.org>

"H . J . Lu" wrote:
> 
> On Wed, Sep 19, 2001 at 09:09:03AM -0700, John Reiser wrote:
> > Here is an integration of -Bsymbolic and --allow-shlib-undefined
> > with diffs against the latest release binutils-2.11.2.
>                                         ^^^^^^^^^^^^^^^^
> That may be too old. Please try CVS, snapshot, the Linux binutils, in
> that order, if you want to submit patches to binutils.

I will look into those alternatives.  But if patches against
the latest release are too old, then that is a sign of a broken
development process.  CVS with branches and release tags
provides explicit, direct support for patching the latest release,
and for merging changes from branch to mainline.  And working from
the latest release guarantees that separate threads of development
are identified and contained, and that interactions are restricted
to known merge points.

-- 
John Reiser, jreiser@BitWagon.com

  reply	other threads:[~2001-09-19 10:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07  8:56 John Reiser
2001-09-10 10:43 ` Nick Clifton
2001-09-19  9:07   ` [PATCH] " John Reiser
2001-09-19  9:13     ` H . J . Lu
2001-09-19 10:53       ` John Reiser [this message]
2001-09-19 12:14       ` John Reiser
2001-09-24 23:38       ` Where can I add "-lm" flag to compile tc-*.c jw c
2001-09-25 11:55   ` optionally postpone assignment of Common John Reiser
2001-09-25 19:13     ` Alan Modra
2001-09-25 21:13       ` John Reiser
2001-09-29  5:58         ` Alan Modra

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=3BA8DC06.7F513F01@BitWagon.com \
    --to=jreiser@bitwagon.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    /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).