Ok. I'm willing to play ball on that. Also since Atlassian products are pretty cool. I just like the idea of a more modern workflow. If I got a vote, which I suppose I don't, It would be git/github, but hg/bitbucket is ok. Git/bitbucket is what I use on the side as well.
--Mark _______________________ Mark E. Anderson <e...@emer.net> On Sun, Mar 16, 2014 at 3:31 PM, Sean Farley <s...@macports.org> wrote: > > Ryan Schmidt <ryandes...@macports.org> writes: > > > On Mar 16, 2014, at 13:27, Ivan Larionov wrote: > > > >> I want to start this discussion mainly about ports tree, but actually > base and some other stuff could use github and infra around it as well. I > understand this is not so easy and may be you already discussed it and may > be already decided not to do, but there are huge pros: > >> > >> * git >> svn > > > > For you, moving from svn to git may be a pro; for me, it would initially > be a con. I have a decade of experience with Subversion and a very good > understanding of how it works and behaves, and only an extremely spotty > understanding of git. It makes me uncomfortable every time I use it. That > could be cured by spending some hours with a fine manual, but it would be > something new to need to learn. Although I understand github does offer svn > access to its git repositories, so it's possible those like me who would > prefer not to be forced to switch to git wouldn't have to. > > Coming from years of supporting projects moving from Subversion to git / > Mercurial, it has been my experience that Mercurial has a much more sane > user interface and doesn't force the user to grok the internals as I've > found git does. > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev >
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
