Re: One version number, &c, take two

[DJ Delorie <dj at redhat dot com>]

> After some shakeout time in gcc only, presumably they could start
> using a similar scheme?  (yes, I would help adapt scripts and
> makefiles as necessary.)

Have you asked to see if they're even interested?

> > Could you commit to both repositories, so that the file stays in sync?
> 
> I'm not sure if I understand the requirement here.  Would it be
> necessary for the nightly GCC cron job to commit the file to each
> repository on every bump?  Or can I just create the file the first
> time and let your sync scripts propagate the nightly bumps?

The scripts just email me, I have to manually sync them.  So you'd
have to have your cron job commit to both repositories.

> What about the other files, which change occasionally?

They're manually sync'd.  The cron job just monitors the two
repositories, and emails a few people when it detects differences.
It's a pain but neither repository is willing to cede control of the
toplevel to the other.

> I honestly don't see the problem here.  There is lots of stuff in
> toplevel, config, and include that is only relevant to a subset of the
> projects in src+gcc.

Sadly, that *is* the problem.  I didn't say it was a big problem, it
just seems like we're heading down a slippery slope.