On Tue, Apr 29, 2014 at 6:00 AM, JonY jon_y@... wrote:
On 4/29/2014 14:49, Rodny wrote:
JonY jon_y@... 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.
Discuss.
There seems to be no possibility of discussion, only talks of acceptance. A
pity. If you do not intend to ever accept an option other than the one you
propose, then do not ask for discussion. It just adds insult to injury.
Hello, world. First time poster, long time user.
I know I'm in the minority, but I'd just like to say that I'm actually
against this change. We use your products in house here almost constantly
(Bob's your uncle for that!), and we really love how easy it is to use your
code base. We always build our own toolchains, and we are setup to
interface directly to you. Switching this up for no apparent reason throws
a giant wrench into our operation. With our staffing, we will be fubar
bundied for all you WW2 buffs out there.
I noticed that everyone in this thread, including this original post, is
coming from the standpoint of why not use git? while I'd like to ask you
the question, Why are you changing?
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 in SVN, not to mention, multi-part commit
patches are nice.
SVN does all of that easily. Are you sure you aren't just using it wrong? The
notion that it does not branch and merge is very outdated. There is even a
whole section in the manual called Cherry Picking.
As far as long term branches, how is svn merge ^/trunk any different than
git pull ?
How will you handle all the various things that you currently distribute?
You have a lot of stuff in your repository, and it all works nicely because
of how svn treats each directory as essentially a separate repo. What are
you going to do about the branches, tags, and experimentals?
Already mentioned in the original email.
Not really. The entire workflow changes drastically, and you've not indicated
at all how users should deal with that.
Have you even considered other distributed systems? Mercurial, Bazaar? Or
is it git all the way just because it's git? Git is much more of a Do
what Linus says project, than it is a tool that's solving a problem.
What does Linus have to do with the decision? If anything, I'll use it
because Linus recommends it.
You ignored the question, which implies the answer is no.
I'd actually like to see you move to a more recent version of svn that has
a lot of new whiz-bang features that make it more desirable to stay with
the status quo. Contrary to popular belief, git doesn't merge/branch any
better than svn, unless you compare brand new git to svn v1.0.
Finally... why not just set up a git mirror like so many other projects do?
Because git commits cannot easily push back to SVN, and great, you have
all the power of git and the inconvenience of SVN.
SVN seems to be an inconvenience to you because you aren't using it correctly.
That's not a deficiency in the tool. And as pointed out, many projects
successfully use a git mirror, including GCC itself.
Your original message said that the project may switch to git. I now
understand that this was not true. It should have said that the project will
switch, and you are entertaining zero other options. Why even bother asking
your community? Why not just tell instead of ask? Your responses reek of
Keith Marshall. This is the kind of thing that drove us away from mingw.org in
the first place. This is not what we have come to expect over the years.
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
