I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that? -- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
This should be fixed now. If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/ You may need to turn on the strip extension in your .hgrc. To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like: [paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt". Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes. -Nathan On Tue, May 12, 2015 at 8:23 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
On Tue, May 12, 2015 at 11:29 AM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
These paths make use of the hgbb extension, but you'll probably use ssh or https paths if you don't have that set up already.
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
Thank you Nathan et al. I am sorry for the hassle I caused to everyone. I've already taken the .hgrc steps recommended here to prevent this in the future. On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Mike, this is all I have to say to you. https://www.youtube.com/watch?v=jG2KMkQLZmI On Tue, May 12, 2015 at 1:42 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
Thank you Nathan et al. I am sorry for the hassle I caused to everyone. I've already taken the .hgrc steps recommended here to prevent this in the future.
On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
Shouldn't we send out an email to yt-users? I imagine this could've affected more than just the developers. On Tue, May 12, 2015 at 11:59 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Mike, this is all I have to say to you.
https://www.youtube.com/watch?v=jG2KMkQLZmI
Thank you Nathan et al. I am sorry for the hassle I caused to everyone. I've already taken the .hgrc steps recommended here to prevent this in
On Tue, May 12, 2015 at 1:42 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote: the
future.
On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the
hgrc
file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hmm, I hadn't thought of that. Nathan's recipe is probably fine to run. FWIW the exact changesets: http://paste.yt-project.org/show/5546/ On Tue, May 12, 2015 at 2:03 PM, Cameron Hummels <chummels@gmail.com> wrote:
Shouldn't we send out an email to yt-users? I imagine this could've affected more than just the developers.
On Tue, May 12, 2015 at 11:59 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Mike, this is all I have to say to you.
https://www.youtube.com/watch?v=jG2KMkQLZmI
On Tue, May 12, 2015 at 1:42 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
Thank you Nathan et al. I am sorry for the hassle I caused to everyone. I've already taken the .hgrc steps recommended here to prevent this in the future.
On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork -- can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ 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
I don't think it'll effect "yt update" in practice, since that updates to the tip of the yt branch. On Tue, May 12, 2015 at 12:05 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hmm, I hadn't thought of that. Nathan's recipe is probably fine to run. FWIW the exact changesets:
http://paste.yt-project.org/show/5546/
On Tue, May 12, 2015 at 2:03 PM, Cameron Hummels <chummels@gmail.com> wrote:
Shouldn't we send out an email to yt-users? I imagine this could've affected more than just the developers.
On Tue, May 12, 2015 at 11:59 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Mike, this is all I have to say to you.
https://www.youtube.com/watch?v=jG2KMkQLZmI
On Tue, May 12, 2015 at 1:42 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
Thank you Nathan et al. I am sorry for the hassle I caused to
everyone.
I've already taken the .hgrc steps recommended here to prevent this in the future.
On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum < nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local copy: http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo.
Here
is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
I accidently pushed to the yt_analysis bitbucket instead of my fork
--
can anyone let me know how to undo that?
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ 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
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I thought "yt update" went to the tip of whatever branch you're on. Perhaps I'm wrong? If we have users who aren't on the yt-dev list but who are using the dev branch, and they ran "yt update" in the 3 hours that this problems was out there, won't they pull these changesets? Perhaps this won't cause problems? But if they ever push those changes elsewhere, I can see the "genie out of the bottle" problem wreaking havoc. On Tue, May 12, 2015 at 12:08 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
I don't think it'll effect "yt update" in practice, since that updates to the tip of the yt branch.
On Tue, May 12, 2015 at 12:05 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hmm, I hadn't thought of that. Nathan's recipe is probably fine to run. FWIW the exact changesets:
http://paste.yt-project.org/show/5546/
On Tue, May 12, 2015 at 2:03 PM, Cameron Hummels <chummels@gmail.com> wrote:
Shouldn't we send out an email to yt-users? I imagine this could've affected more than just the developers.
On Tue, May 12, 2015 at 11:59 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Mike, this is all I have to say to you.
https://www.youtube.com/watch?v=jG2KMkQLZmI
On Tue, May 12, 2015 at 1:42 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
Thank you Nathan et al. I am sorry for the hassle I caused to
everyone.
I've already taken the .hgrc steps recommended here to prevent this in the future.
On Tue, May 12, 2015 at 2:29 PM, Nathan Goldbaum < nathan12343@gmail.com> wrote:
This should be fixed now.
If you pulled during the time when the bad changes were available on the main yt repo, you will need to strip some changes in your local
copy:
http://paste.yt-project.org/show/5546/
You may need to turn on the strip extension in your .hgrc.
To prevent this from happening in the future, I'd strongly urge contributors to *not* have yt_analysis/yt as the default path in the hgrc file for the repo (located at $YT_REPO/.hg/hgrc). Instead, point your default path at your fork and add an alias for the main yt repo. Here is what my repo's hgrc looks like:
[paths] default = bb://ngoldbaum/yt mainyt = bb://yt_analysis/yt
To pull from yt_analysis/yt, I just do "hg pull mainyt". I *never* do "hg push mainyt".
Please let us know if you encounter any issues related to this. Sorry it took so long to fix, but apparently we triggered a bug in bitbucket's PR handling code that one of the bitbucket engineers had to work around to manually strip the changes.
-Nathan
On Tue, May 12, 2015 at 8:23 AM, Michael Zingale <michael.zingale@stonybrook.edu> wrote: > > I accidently pushed to the yt_analysis bitbucket instead of my fork -- > can anyone let me know how to undo that? > > -- > Michael Zingale > Associate Professor > > Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, > NY > 11794-3800 > phone: 631-632-8225 > e-mail: Michael.Zingale@stonybrook.edu > web: http://www.astro.sunysb.edu/mzingale > > _______________________________________________ > 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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ 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
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ 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
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Cameron Hummels -
Matthew Turk -
Michael Zingale -
Nathan Goldbaum