Re: [Mingw-w64-public] stdio_s.h and 4.9.0 mingw

2014-04-28 Thread Kai Tietz
Hi, this issue should be already solved on trunk. So I guess you are using 3.x version, aren't you? Regards, Kai -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium

Re: [Mingw-w64-public] stdio_s.h and 4.9.0 mingw

2014-04-28 Thread Alexpux
28 апр. 2014 г., в 14:51, Kai Tietz ktiet...@googlemail.com написал(а): Hi, this issue should be already solved on trunk. So I guess you are using 3.x version, aren't you? Yes, x86_64-4.9.0-release-win32-seh-rt_v3-rev0.7z have mingw-w64 v3 from trunk. Regards, Alexey. Regards, Kai

[Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread JonY
Hi, mingw-w64 may migrate from svn to git in the future, seeing that sf can now do multiple repos per project. Structure wise, everything under trunk will still stay together in the new repo, but any externals, /experimental/* and /web may move into its own repo. Discuss. signature.asc

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Kai Tietz
Hi, as JonY said, do we think about switching to git. Of couse such a step might shows side-effects to our users. So we would like to get your opinion and thoughts for this step. As svn-repository works a bit different as git, we will need to restructure our branches, tags, trunk, and

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Koehne Kai
-Original Message- From: JonY [mailto:jo...@users.sourceforge.net] Hi, mingw-w64 may migrate from svn to git in the future, seeing that sf can now do multiple repos per project. Structure wise, everything under trunk will still stay together in the new repo, but any

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Ruben Van Boxem
2014-04-28 13:30 GMT+02:00 Kai Tietz ktiet...@googlemail.com: Hi, as JonY said, do we think about switching to git. Of couse such a step might shows side-effects to our users. So we would like to get your opinion and thoughts for this step. As svn-repository works a bit different as git,

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread JonY
On 4/28/2014 19:53, Ruben Van Boxem wrote: Different repositories may sound like a nice idea, but keeping them in sync can be a pain, depending on the complexity of the subprojects. I believe stuff like ironcrate, winpthreads and perhaps the mingw-w64-tools folder deserve their own repo, as

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: On 4/28/2014 19:53, Ruben Van Boxem wrote: Different repositories may sound like a nice idea, but keeping them in sync can be a pain, depending on the complexity of the subprojects. I believe stuff like ironcrate,

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread John E. / TDM
On 4/28/2014 5:17 AM, JonY wrote: mingw-w64 may migrate from svn to git in the future, seeing that sf can now do multiple repos per project. *snip* Discuss. I'm a bit surprised at the choice of Git -- in my experience, Windows developers usually prefer Mercurial

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: On 4/28/2014 19:53, Ruben Van Boxem wrote: Different repositories may sound like a nice idea, but keeping them in sync can be a pain, depending on the complexity of the

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Matthew Brett
Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM tdra...@tdragon.net wrote: On 4/28/2014 5:17 AM, JonY wrote: mingw-w64 may migrate from svn to git in the future, seeing that sf can now do multiple repos per project. *snip* Discuss. I'm a bit surprised at the choice of Git -- in my

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Jon
On Mon, Apr 28, 2014 at 10:03 AM, LRN lrn1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: On 4/28/2014 19:53, Ruben Van Boxem wrote: Different repositories may sound like a nice idea, but keeping them in sync can be a pain, depending

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
On Mon, Apr 28, 2014, JonY wrote: Hi, mingw-w64 may migrate from svn to git in the future, seeing that sf can now do multiple repos per project. Structure wise, everything under trunk will still stay together in the new repo, but any externals, /experimental/* and /web may move into its

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
On Mon, Apr 28, 2014, Jon wrote: On Mon, Apr 28, 2014 at 10:03 AM, LRN lrn1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: On 4/28/2014 19:53, Ruben Van Boxem wrote: Different repositories may sound like a nice idea, but keeping

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 22:42, Adrien Nader wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM tdra...@tdragon.net wrote: On 4/28/2014 5:17 AM, JonY wrote: mingw-w64 may migrate from svn to git in the

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Matthew Brett
Hi, On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM tdra...@tdragon.net wrote: On 4/28/2014 5:17 AM, JonY wrote: mingw-w64 may migrate from svn to git in the future, seeing

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 22:42, Adrien Nader wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM tdra...@tdragon.net wrote: On 4/28/2014 5:17 AM, JonY wrote:

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Jacek Caban
On 04/28/14 13:17, JonY wrote: Discuss. I will just add a huge YEAH from me. I'm happy to help with the migration. Cheers, Jacek -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Matthew Brett
On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 22:42, Adrien Nader wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM tdra...@tdragon.net wrote: On 4/28/2014 5:17 AM, JonY wrote:

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Adrien Nader
One more note on the TODO: chose how commits are organized. I like: feature branches (I think everyone does) and rebase on master before merge provided the branch hasn't been merged elsewhere too. This gives a linear history which is much nicer than octopuss-shaped graphs. In case anyone doubts

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Matthew Brett
Hi, On Mon, Apr 28, 2014 at 12:38 PM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, Matthew Brett wrote: Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 23:29, Matthew Brett wrote: On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 22:42, Adrien Nader wrote: On Mon, Apr

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Matthew Brett
Hi, On Mon, Apr 28, 2014 at 1:05 PM, LRN lrn1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 23:29, Matthew Brett wrote: On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread John E. / TDM
On 4/28/2014 12:11 PM, Jon wrote: Regarding git vs. mercurial on windows, I use both on a daily basis, like both, but prefer git. The only performance complaint I've had relates to garbage collection. If you try to `git gc --aggressive --prune=now` a large repo, you'll often find that the

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Jon
On Mon, Apr 28, 2014 at 2:32 PM, Adrien Nader adr...@notk.org wrote: On Mon, Apr 28, 2014, Jon wrote: On Mon, Apr 28, 2014 at 10:03 AM, LRN lrn1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: On 4/28/2014 19:53, Ruben Van

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

2014-04-28 Thread Óscar Fuentes
Adrien Nader adr...@notk.org writes: I quite dislike github and its UI in particular. Uses flash on every page (no idea what for) and lots of javascript which makes my laptop heat and get noisy when displaying something as small as a 3-lines diff. I see no flash at all on Github (it is