On Tue, 26 Jun 2007, Martin Rubey wrote:
| Dear Gaby,
|
| Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
|
| > It is obvious to me that automated version updated can run as follows:
| >
| > * daily bump: anywhere, preferably a machine that is almost always
| > up -- we can use the c
Dear Gaby,
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> It is obvious to me that automated version updated can run as follows:
>
> * daily bump: anywhere, preferably a machine that is almost always
> up -- we can use the cron job facility at SF.
Yes, of course. But suppose that
Martin --
It is obvious to me that automated version updated can run as follows:
* daily bump: anywhere, preferably a machine that is almost always
up -- we can use the cron job facility at SF.
* release with version number: this should be done when the
release is mad
On Tue, 26 Jun 2007, Ralf Hemmecke wrote:
| Hi Gaby, Cliff, Martin,
|
| isn't that a bit of overkill if the script updates every file?
The script I sent does not update every file.
It modifies only a handful of GCC files: exclusively those that
contain version information.
In case of Axiom, it
Hi Gaby, Cliff, Martin,
isn't that a bit of overkill if the script updates every file?
SVN is different from CVS, there are global revision numbers. So it is
simply enough if there is one file that contains some specific version
information. (I guess the same is true for any newer SCM like git
Cliff --
You don't need to have separate programs for sepaerate branches.
Please find attached the script
$GCC/maintainer-scripts/update_version_svn
that we use for GCC. It is reltively simple. It was originally written
for our CVS repository and quickly adapted to SVN -- without modif
