From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: DJ Delorie <dj@delorie.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@redhat.com
Subject: Re: Top level: Separate src release scripts from Makefile
Date: Sun, 29 Sep 2002 15:23:00 -0000 [thread overview]
Message-ID: <20020929221923.GA5246@doctormoo.dyndns.org> (raw)
In-Reply-To: <200209292212.g8TMCv813264@envy.delorie.com>
On Sun, Sep 29, 2002 at 06:12:57PM -0400, DJ Delorie wrote:
>
> I'm thinking perhaps the release stuff should be in a package-specific
> subdirectory? Like the binutils release script should be in
> src/binutils, and the gdb release script in src/gdb ?
Good idea, but it requires an order of magnitude more work to get right;
I'd much rather do it after I manage to get it disentangled from
Makefile.in.
Also, there's an awful lot of shared code at the moment and it might be
desirable to keep it shared. (Although I can actually think of two
rather elegant solutions using autogen...)
> And I also agree that src/Makefile.in should not itself be used to do
> releases. That's just icky.
next prev parent reply other threads:[~2002-09-29 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 9:56 top level: make more dependencies explicit Nathanael Nerode
2002-09-29 10:09 ` Andrew Cagney
2002-09-29 10:30 ` Nathanael Nerode
2002-09-29 10:45 ` Andrew Cagney
2002-09-29 12:51 ` Daniel Jacobowitz
2002-09-29 12:58 ` H. J. Lu
[not found] ` <20020929174544.GA30373@doctormoo.dyndns.org>
[not found] ` <3D974828.4050009@redhat.com>
[not found] ` <20020929190100.GA31652@doctormoo.dyndns.org>
[not found] ` <3D9764F8.7000100@redhat.com>
2002-09-29 14:50 ` Top level: Separate src release scripts from Makefile Nathanael Nerode
2002-09-29 15:13 ` DJ Delorie
2002-09-29 15:23 ` Nathanael Nerode [this message]
2002-09-30 11:47 ` Alexandre Oliva
2002-09-30 9:49 ` top level: make more dependencies explicit DJ Delorie
2002-09-29 14:59 Top level: Separate src release scripts from Makefile Nathanael Nerode
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=20020929221923.GA5246@doctormoo.dyndns.org \
--to=neroden@doctormoo.dyndns.org \
--cc=binutils@redhat.com \
--cc=dj@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.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