I've created this changest with a spoofed date the day after the last
commit to the yt-3.0 branch, in case anyone cares about date sorting
commits.
https://bitbucket.org/ngoldbaum/yt/commits/30566bbec83d863f902a297226cf22b9d...
On Thu, Sep 10, 2015 at 5:43 PM, John ZuHone
+1
John ZuHone Kavli Center for Astrophysics and Space Research Massachusetts Institute of Technology 77 Massachusetts Ave., 37-582G Cambridge, MA 02139 (w) 617-253-2354 (m) 781-708-5004 jzuhone@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com
On Sep 10, 2015, at 6:38 PM, Nathan Goldbaum
wrote: Hi all,
I just noticed today that the yt-3.0 branch still shows up in "hg branches" for fresh clones of the main yt repository. I think that was done on purpose so that changes on the yt-3.0 branch could be included into the yt branch after the point when the merged yt-3.0 into the yt branch heading up to the release of yt-3.0.
At this point, I think we've long passed the time when people might want to submit pull requests from the yt-3.0 branch. I can make it so that the yt-3.0 branch will no longer show up in "hg branches" or more importantly in the branch dropdown menu for commits or pull requests on bitbucket by creating a --close-branch commit on the yt-3.0 branch. The yt-3.0 branch will still live on in history and will also show up in "hg branches --closed".
Unfortunately, it seems I can't make a pull request that includes only a branch closing commit. Would anyone object to me pushing such a commit directly to yt_analysis/yt?
-Nathan
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org