public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Christian Cornelssen <ccorn@cs.tu-berlin.de>
Cc: Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
	 <gdr@integrable-solutions.net>,  <gcc@gcc.gnu.org>
Subject: Re: Info-files missing in gcc 3.2.2
Date: Thu, 06 Feb 2003 20:20:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0302062014070.14311-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0302061849150.2576-100000@Dachs.Bau>

On Thu, 6 Feb 2003, Christian Cornelssen wrote:

> added. "cvs rdiff" would not be affected. If you mean diffs between
> actual release tar contents, then this would matter for diff users
> without makeinfo.

I mean the diffs supplied between the release tarballs.

> inconvenience of having to install makeinfo. Don't you think that
> typical users will download gcc-3.2.2.tar.*z*, regardless of whether
> versions with additional suffixes exist?

I expect they would have downloaded gcc-3.2.tar.*z* when 3.2 came out,
downloaded the diffs to 3.2.1 (not the whole tarball) when 3.2.1 came out,
the diffs to 3.2.2 (which remove the info files) when 3.2.2 came out and
will download the diffs to 3.2.3 when 3.2.3 comes out.  To build 3.2.3
they will unpack the tarball and apply successive diffs; this will fail if
the 3.2.3 diffs patch info files in the expectation they were present,
because they were generated against an updated release tarball.  The diffs
are exact diffs between the tarball contents (provided you apply them with
GNU patch; otherwise, diffs between binary message catalogs might cause
problems).

-- 
Joseph S. Myers
jsm28@cam.ac.uk

  parent reply	other threads:[~2003-02-06 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06  9:46 Volker Reichelt
2003-02-06 15:48 ` Christian Cornelssen
2003-02-06 16:01   ` Herbert Schmid
2003-02-06 17:44   ` Joseph S. Myers
2003-02-06 18:28     ` Christian Cornelssen
2003-02-06 19:47       ` Gerald Pfeifer
2003-02-06 20:20       ` Joseph S. Myers [this message]
2003-02-06 21:31       ` Joe Buck
2003-02-06 20:24     ` Volker Reichelt

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=Pine.LNX.4.33.0302062014070.14311-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=ccorn@cs.tu-berlin.de \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=reichelt@igpm.rwth-aachen.de \
    /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).