Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>
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 11:36:00 -0000	[thread overview]
Message-ID: <3D974828.4050009@redhat.com> (raw)
In-Reply-To: <20020929174544.GA30373@doctormoo.dyndns.org>


>> The mechanism is very old (it pre-dates me as GDB release engineer). 
>> Changing it is going to involve updates to many things - snapshot 
>> scripts, release process doco, .... so won't happen overnight.
> 
> 
> Mmmm.  I'm going to start rewriting it now. >:-=

What does the GNU coding standard have to say about the release process?

I'd also be wary of a ``rewrite'', the top-level stuff iteracts with 
sub-directories in strange ways.  I think reserving the existing 
behavior (but perhaphs outside of the Makefile.in) would be a better 
incremental step.

Also, how does this compare to GCC's release process.

Andrew



  reply	other threads:[~2002-09-29 18:36 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 [this message]
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

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=3D974828.4050009@redhat.com \
    --to=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=neroden@doctormoo.dyndns.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