<div dir="ltr">Hi all,<div><br></div><div>I received very few replies for this, so I don't think it's worth the effort to merge multiple separate PRs into one.</div><div><br></div><div>Alex</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Oct 10, 2013 at 12:25 AM, Alex Gaudio <span dir="ltr"><<a href="mailto:adgaudio@gmail.com" target="_blank">adgaudio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi everyone,<div><br></div><div>I've been looking at some of the PRs on GitHub, and would love to see them integrated into StarCluster. I'm sure a few of you would also like to see some of these PRs merged as well.</div>
<div><br></div><div>In the interest of speeding things up and helping @jtriley out a bit, I'm considering rebasing some of these outstanding PRs into the vpc branch (which is now, to my knowledge, fully backwards compatible with StarCluster). The idea would be that when we merge this branch into develop, we will close a lot of outstanding pull requests in one go.</div>
<div><br></div><div>What are everyone's thoughts on this? It would require a well coordinated effort to not merge/rebase the same PR twice and then wind up with terrible merge conflicts. On the other hand, if we knew not to merge PR #X directly (via a comment in the PR), then this seems like a really doable way to get a lot of new features into StarCluster.</div>
<div><br></div><div>@jtriley, I'm specifically interested in what you think about this, since you control the repo.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Alex</div></font></span></div>
</blockquote></div><br></div>