This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfa] more ``releasing GDB'' review


> Date: Thu, 24 Jan 2002 12:21:03 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> Here is further updates to the how-to-release notes based on doing 5.1.1.

I have a few routine comments:

> + ARI is an @kbd{awk} script (Awk Regression Indicator?) that checks for a

"awk" should be in @code (it's a name of a program, not something you
type).

> ! the core documentation.  That might be worth persuing.}

I think you meant "pursuing".

> + @var{AM_INIT_AUTOMAKE}.  Tweek it to read something like

"Tweak".

> ! @emph{Don't worry about the @file{gdb.info-??} or
> ! @file{gdb/p-exp.tab.c}.  They were generated (and yes @file{gdb.info-1}
> ! was also generated only something strange with CVS means that they
> ! didn't get supressed).  Fixing it would be nice though.}

Isn't this a problem with .cvsignore?

> + NB: A pipe such as @kbd{bunzip2 < xxx.bz2 | gzip -9 > xxx.gz} shouldn't
> + be used since, in that mode, gzip doesn't know the file name information
> + and consequently can't include it.  This is also why the release process
> + runs @kbd{tar} and @kbd{bzip2} as separate passes.

"tar" and "bzip2" in the last sentence should be in @code.

> + @item
> + create a @file{htdocs/<version>} directory (eg @file{htdocs/5.1.1}.

I siggest to write @var{version} instead of <version>.  And that "eg"
should be "e.g.,", I think.

> + Don't forget the ChangeLog

This needs a period at the end.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]