On Sun, Feb 17, 2013 at 10:07 PM, Eric Seidel <span dir="ltr"><<a href="mailto:eric@webkit.org" target="_blank">eric@webkit.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Feb 17, 2013 at 9:54 PM, Maciej Stachowiak <<a href="mailto:mjs@apple.com">mjs@apple.com</a>> wrote:<br>
><br>
> There's probably proportionately more people using Git. Making these web surveys is a pain, so I'd rather not do it again if we don't need to.<br>
><br>
> What would be the pros and cons of the master repository being git instead of svn, for git users?<br></div></blockquote><div><br></div><div>As far as I could recall the last discussion, there won't be much benefit in switching the master over to git unless we adopt git workflow (e.g. first new links on <a href="https://www.google.com/search?q=git+workflow">https://www.google.com/search?q=git+workflow</a>). In particular, change loges are the biggest obstacle.</div>
<div><br></div><div>We could try to mitigate this divergence by allowing webkit-patch to fill in change logs automatically from git commit messages when landing patches. (I'm not volunteering to do this).</div><div><br>
</div><div>This involves commands like "webkit-patch upload" automatically pre populating git commit messages (without modifying change logs) as they do change logs today, and then commands like "webkit-patch land" automatically parsing those git commit messages to populate change logs and commit --amend them. Commands like "webkit patch apply-from-bug" can then parse change log changes and convert them to git commit messages in turn.</div>
<div><br></div><div>I'm not sure how change logs should be updated/constructed in branch-merge workflow.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But that's not really an argument I'm interested in pushing. I<br>
believe eventually the remaining SVN users will switch to distributed<br>
version control of their own will, and we'll eventually decide to stop<br>
supporting SVN because not enough of the project is using it to<br>
justify causing the majority of users to use a translated solution.<br></blockquote><div><br></div><div>FWIW, I don't plan to use git or any other distributed VCS in contributing to WebKit. I like svn's simplicity.</div>
<div><br></div><div>- R. Niwa</div><div><br></div></div>