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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04.05.2014 20:06, LRN wrote: > On 04.05.2014 19:50, Dongsheng Song wrote: >> On Sun, May 4, 2014 at 10:09 PM, JonY wrote: >>> On 5/4/2014 12:17, NightStrike wrote: Now... that said, there's a few things that I didn't see addressed a

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

On Mon, May 05, 2014, JonY wrote: > > This is a simple change in vim's configuration file (in the case SF > > doesn't changing that in some Web UI). I don't think I can check on > > jon_y's repo (seems I don't have the rights to access it through ssh). > > > > Right now, I made it readonly except

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

On 5/5/2014 04:27, Adrien Nader wrote: > tl:dr; agreed > > Also, something not mentioned elsewhere and which I didn't know where to > put: a large appeal of git in mingw-w64 is coherency with other source > repositories. One less tool to master. > > On Sun, May 04, 2014, NightStrike wrote: >> Res

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

tl:dr; agreed Also, something not mentioned elsewhere and which I didn't know where to put: a large appeal of git in mingw-w64 is coherency with other source repositories. One less tool to master. On Sun, May 04, 2014, NightStrike wrote: > Responding to both of you inline... sort it out :P > >> a

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

Responding to both of you inline... sort it out :P On Sun, May 4, 2014 at 10:24 AM, Adrien Nader wrote: > On Sun, May 04, 2014, JonY wrote: >> On 5/4/2014 12:17, NightStrike wrote: >> > >> > Now... that said, there's a few things that I didn't see addressed >> > anywhere in this thread. >> > >> >

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04.05.2014 19:50, Dongsheng Song wrote: > On Sun, May 4, 2014 at 10:09 PM, JonY wrote: >> On 5/4/2014 12:17, NightStrike wrote: >>> >>> Now... that said, there's a few things that I didn't see addressed >>> anywhere in this thread. >>> >>> 1) Jon

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

On Sun, May 4, 2014 at 10:09 PM, JonY wrote: > On 5/4/2014 12:17, NightStrike wrote: >> >> Now... that said, there's a few things that I didn't see addressed >> anywhere in this thread. >> >> 1) Jon, you had asked me to setup a mailing list for svn commits. I >> did so. Then SF added their own t

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

On Sun, May 04, 2014, JonY wrote: > On 5/4/2014 12:17, NightStrike wrote: > > > > Now... that said, there's a few things that I didn't see addressed > > anywhere in this thread. > > > > 1) Jon, you had asked me to setup a mailing list for svn commits. I > > did so. Then SF added their own thing

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

On 5/4/2014 12:17, NightStrike wrote: > > Now... that said, there's a few things that I didn't see addressed > anywhere in this thread. > > 1) Jon, you had asked me to setup a mailing list for svn commits. I > did so. Then SF added their own thing that just sends the commit > message without th

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

Wow, I really have been away for a long time. I found this thread while cleaning things out now that my 578493578943 projects at work are finally finishing. Also, I'm trying to see if we can incorporate winpthreads in one project :) I have to say, this is kind of sad, mostly because of 1) misinf

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

2014-04-30 20:05 GMT+02:00 JonY : > Experimentals are outdated and unused and has not seen any > changes for a long time, and unlikely to see any significant changes soon. > The only gem left in experimental is ironcrate, which is still far from > complete, I doubt there are actually active ironcra

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

On 4/30/2014 21:34, Rodny Spillig wrote: >> >> Because it was a pain to track down patches applied to other branches >> and reapply it again and again, cherry-pick is god sent. Not to mention >> merging is quick and simple. It is also far far easier to do a long term >> private branch in git than i

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

On Tue, Apr 29, 2014 at 6:00 AM, JonY wrote: > On 4/29/2014 14:49, Rodny wrote: >> JonY writes: >> >>> >>> 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 to

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

On 4/30/2014 19:52, JonY wrote: > On 4/30/2014 19:18, Ruben Van Boxem wrote: >> 2014-04-30 12:45 GMT+02:00 JonY : >> >>> Hi, >>> >>> I have enabled read-only access to the git repos for testing purposes, >>> the experimental directory is mostly outdated and can be left in SVN. >>> >>> Do try out th

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

On 4/30/2014 19:52, JonY wrote: >> Another small nit: the branches still have tags, (v1.0 and v2.0), maybe get >> rid of these for confusion's sake. >> > Wait, I don't see them(???) All I see is: Branches master v1.x v1.x@4408 v1.x@4409 v2.x v2.x@4408 v2.x@4410 v3

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

On 4/30/2014 19:18, Ruben Van Boxem wrote: > 2014-04-30 12:45 GMT+02:00 JonY : > >> Hi, >> >> I have enabled read-only access to the git repos for testing purposes, >> the experimental directory is mostly outdated and can be left in SVN. >> >> Do try out the repos (git clone URL): >> >> mingw-w64

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

2014-04-30 12:45 GMT+02:00 JonY : > Hi, > > I have enabled read-only access to the git repos for testing purposes, > the experimental directory is mostly outdated and can be left in SVN. > > Do try out the repos (git clone URL): > > mingw-w64 proper - git://git.code.sf.net/p/mingw-w64/git > webpag

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

Hi, I have enabled read-only access to the git repos for testing purposes, the experimental directory is mostly outdated and can be left in SVN. Do try out the repos (git clone URL): mingw-w64 proper - git://git.code.sf.net/p/mingw-w64/git webpage - git://git.code.sf.net/p/mingw-w64/git-web iron

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

On 4/29/2014 14:49, Rodny wrote: > JonY writes: > >> >> 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, /experimenta

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29.04.2014 11:31, Ruben Van Boxem wrote: > On 2014-04-29 8:49 GMT+02:00 Rodny: > >> JonY writes: >> >>> >>> Hi, >>> >>> mingw-w64 may migrate from svn to git in the future, seeing that sf >>> can now do multiple repos per project. >>> >>> Stru

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

Rodny writes: > Ignoring the endless holy wars, some practical concerns that we have here > are the dismal support on native windows for git. TortoiseSVN makes > browsing your changes and picking the ones we want extremely easy in a > graphical environment on the platform that you're built to pro

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

Hi, On Mon, Apr 28, 2014 at 11:49 PM, Rodny wrote: > JonY writes: > >> >> 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 exte

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

2014-04-29 8:49 GMT+02:00 Rodny : > JonY writes: > > > > > 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, /ex

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

JonY writes: > > 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.

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

Adrien Nader 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 activated only on r

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

On Mon, Apr 28, 2014 at 2:32 PM, Adrien Nader wrote: > On Mon, Apr 28, 2014, Jon wrote: > > On Mon, Apr 28, 2014 at 10:03 AM, 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: >

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

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 th

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

Hi, On Mon, Apr 28, 2014 at 1:05 PM, LRN 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 wrote: >>> On Mon, Apr 28, 2014, LRN wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>

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

-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 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

Hi, On Mon, Apr 28, 2014 at 12:38 PM, Adrien Nader wrote: > On Mon, Apr 28, 2014, Matthew Brett wrote: >> Hi, >> >> On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader wrote: >> > On Mon, Apr 28, 2014, Matthew Brett wrote: >> >> Hi, >> >> >> >> On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM >> >> w

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

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 it

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

On Mon, Apr 28, 2014, Matthew Brett wrote: > Hi, > > On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader wrote: > > On Mon, Apr 28, 2014, Matthew Brett wrote: > >> Hi, > >> > >> On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM wrote: > >> > On 4/28/2014 5:17 AM, JonY wrote: > >> >> mingw-w64 may migrat

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

On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader 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.

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

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 y

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

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 > >> wrote: > >>> On 4/28/2014 5:17 AM, JonY wrote: >

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

Hi, On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader wrote: > On Mon, Apr 28, 2014, Matthew Brett wrote: >> Hi, >> >> On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM 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

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

-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 >> wrote: >>> On 4/28/2014 5:17 AM, JonY wrote: mingw-w64 may migrate from svn to git in the futur

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

On Mon, Apr 28, 2014, Matthew Brett wrote: > Hi, > > On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM 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'

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

On Mon, Apr 28, 2014, Jon wrote: > On Mon, Apr 28, 2014 at 10:03 AM, 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 t

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

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

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

On Mon, Apr 28, 2014 at 10:03 AM, 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

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

Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM 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 experience, Win

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

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

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

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

-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 ironc

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

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 13:30 GMT+02:00 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 >

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

> -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 an

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

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 experiment

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

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 Descri