On Sun, Aug 03, 2008 at 02:38:45PM +0200, silverdr@inet.com.pl wrote: > Bingo - that means also that Joe The Ordinary won't have to re- > download and recompile every full snapshot. Most users (especially Windows users) are probably glad not to have to recompile the sources themselves:-) > My guess would be that those would tags on the main branch but > probably this comes from your legacy structures, right? No. Here is a layout sample of the repository: trunk ^ | branches/version-2.12/trunk | ^ | | | +-----------> branches/version-2.12/tags/version-2.12.1 | | | | +---------------+-----------> branches/version-2.12/tags/version-2.12.0 : : : | branches/version-2.11/trunk | ^ | | | +-----------> branches/version-2.11/tags/version-2.11.1 | | | | +---------------+-----------> branches/version-2.11/tags/version-2.11.0 | : That means: For a major release, the trunk is branched into the branches directory with a new trunk. This branch is then tagged for the different minor releases. > This doesn't seem like a SVN repository problem but the checked out > trunk sources don't build ATM here: This is caused by changes in the compiler. Things like this may also happen with the snapshot. The C standard says that a label must always be followed by a statement. The _scanf.c source violated this rule, but older versions of the compiler didn't complain. So in fact the _scanf.c file has been broken before, but it went unnoticed. Thanks for the feedback! Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Aug 3 15:03:21 2008
This archive was generated by hypermail 2.1.8 : 2008-08-03 15:03:24 CEST