<div dir="ltr">On Thu, Mar 14, 2013 at 3:56 PM, Martin Ellis <span dir="ltr"><<a href="mailto:ellism88@gmail.com" target="_blank">ellism88@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>So... as per claiming commits I think we have two options...<br></div><br> 1) People add the emails I set to their git-hub profiles and we let the commits automaticly (or via support) be assigned to their accounts.<br>
</div></div></div></blockquote><div><br></div><div style>To do this, I did the following:</div><div style><br></div><div style>1. I clicked on my name in the upper right-hand corner.</div><div style>2. Clicked on "Edit Your Profile"</div>
<div style>3. Clicked on "Emails"</div><div style>4. Added the missing email address.</div><div style>5. (Unnecessarily) clicked "verify." (A verify email had already been sent.)</div><div style>6. Clicked on the link the verification email.</div>
<div style>7. PROFIT.</div><div style><br></div><div style>Well, traditionally it's three steps to PROFIT, but the point being that it was painless.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>
</div> 2) People send me an email address they already have assosiated with git-hub I rewrite the history again and repush the repositry.<br></div></div></blockquote><div><br></div><div style>We could do this, but it is probably unnecessary. (I wanted to walk through step one before I made that claim.)</div>
<div style><br></div><div style>Are there other things we might want to do to this repository before we were to "move" to it? There are certainly other questions and concerns.</div><div style><br></div><div style>
How best to handle branches? Do we export those separately, and then use git to merge things together? Or, do we do any branch merging/resolution first, and then move? (The former is easier, in some ways, but I don't know what makes the most sense.)</div>
<div style><br></div><div style>Some of the branches can go away, but some have things that I would like to hold on to. For example, last year a student started working on library/port of Carl's new scheduler; that code should be brought over. It could be done either by 1) saving the branch and merging the code, or 2) merging into the trunk and then re-running. (At that point, we should think about all of the branches, to save the number of export/import cycles.)</div>
<div style><br></div><div style>Opinions?</div><div style><br></div><div style>Cheers,</div><div style>Matt</div><div style><br></div></div></div></div>