This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: Patch to gcc_update to include revision number in LAST_UPDATED

From: Mike Stump <mrs at apple dot com>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
Date: Tue, 1 Nov 2005 12:07:28 -0800
Subject: Re: Patch to gcc_update to include revision number in LAST_UPDATED
References: <Pine.LNX.4.64.0511010144090.25181@digraph.polyomino.org.uk> <2A3D9DD7-97E0-4444-B2F9-238756F99D9C@apple.com> <1130816768.17866.43.camel@linux-009002242193> <53B8778B-0CED-419F-B434-2B1419B8F1D9@apple.com> <1130874937.7280.32.camel@IBM-82ZWS052TEN.watson.ibm.com>

On Nov 1, 2005, at 11:55 AM, Daniel Berlin wrote:

Can't they simply record what revision they exported?

Yes, getting them to change the export step, say, to put the version number inside the file hierarchy somewhere, and then have the build step use that, would work as well. We can then have gcc_update note inside that same file, the version number as well.

Follow-Ups:
- Re: Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Geoffrey Keating

References:
- Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Joseph S. Myers
- Re: Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Mike Stump
- Re: Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Daniel Berlin
- Re: Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Mike Stump
- Re: Patch to gcc_update to include revision number in LAST_UPDATED
  - From: Daniel Berlin

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