Joined: 01 Jun 2005, 10:36 Location: The Netherlands
Added link to a read-only svn mirror (updated hourly), provided by caspring.org. Thanks det for setting it up!
This will be practical for those who want to continue developing if the server is down. (By SVN switching to the mirror you can continue making diffs, accessing history, etc., just not committing.)
smoth:
Stacktracer for 0.76b1 probably won't get up again because I lost the debugging symbols (they were only at server6 and UF main server; I consider them a bit too big to backup).
Setting up the stacktracer for SVN builds is theoretically possible; it's tightly coupled to the mingw buildbot installer builds tho, so I'd first have to set up that again, and then only if the person hosting this buildslave (LordMatt possibly) doesn't mind uploading 130-200 M after every build the stacktrace thing can be set up at any place having php, a huge amount of diskspace, and the i586-mingw32msvc-addr2line commandline tool (possibly plain addr2line works too).
I've got spare invites on github if you want to use this form of development. When svn goes back up, you'll be able to simply commit a patch from a branch or whatever suits you.
Added link to a read-only svn mirror (updated hourly), provided by caspring.org. Thanks det for setting it up!
This will be practical for those who want to continue developing if the server is down. (By SVN switching to the mirror you can continue making diffs, accessing history, etc., just not committing.)
smoth:
Stacktracer for 0.76b1 probably won't get up again because I lost the debugging symbols (they were only at server6 and UF main server; I consider them a bit too big to backup).
Setting up the stacktracer for SVN builds is theoretically possible; it's tightly coupled to the mingw buildbot installer builds tho, so I'd first have to set up that again, and then only if the person hosting this buildslave (LordMatt possibly) doesn't mind uploading 130-200 M after every build the stacktrace thing can be set up at any place having php, a huge amount of diskspace, and the i586-mingw32msvc-addr2line commandline tool (possibly plain addr2line works too).
Tobi I'd rather host the stack tracer itself (I have php, apache, etc all working already) than upload 130M-200M after every build.
Joined: 16 Oct 2004, 18:40 Location: I still have more posts than you.
I appreciate the link and I will bookmark it but... that thing is a hellmess of half-explanations and is full of minor change spam that crowds out the major differences... I'll take my incomplete but nicely formatted changelog.txt.
Someone with bigger balls than me make a post: PUT YOUR MAJOR CHANGES IN CHANGELOG.TXT OR IT DIDN'T HAPPEN.
Putting documentation (even changelog stuff) in the source control never works.
Put it on a wiki page and I guarantee you'll see it become useful very quick. I guarantee this because I've witnessed the same thing happen in Fedora, Ubuntu, and Wine.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum