From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: top level: make more dependencies explicit
Date: Sun, 29 Sep 2002 15:25:00 -0000 [thread overview]
Message-ID: <87smzs4etl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <3D974828.4050009@redhat.com>
>>>>> "Andrew" == Andrew Cagney <ac131313@redhat.com> writes:
Andrew> What does the GNU coding standard have to say about the
Andrew> release process?
That `make dist' should make a distribution, and that it should ensure
that non-source files in the distribution (e.g., yacc output, info
files, etc), are up to date.
The standards don't say anything about how this is to be implemented.
It is perfectly reasonable to have the dist target run some random
shell script (that is provided in the distribution).
Tom
prev parent reply other threads:[~2002-09-29 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020929165232.GA27545@doctormoo.dyndns.org>
[not found] ` <3D9733C2.2010405@redhat.com>
[not found] ` <20020929172608.GA27678@doctormoo.dyndns.org>
[not found] ` <3D973C44.6090601@redhat.com>
2002-09-29 10:49 ` Nathanael Nerode
2002-09-29 11:36 ` Andrew Cagney
2002-09-29 12:05 ` Nathanael Nerode
2002-09-29 13:39 ` Andrew Cagney
2002-09-29 12:25 ` Zack Weinberg
2002-09-29 15:25 ` Tom Tromey [this message]
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=87smzs4etl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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