[Yt-svn] commit/yt: 3 new changesets
Bitbucket
commits-noreply at bitbucket.org
Fri Feb 25 20:17:36 PST 2011
3 new changesets in yt:
http://bitbucket.org/yt_analysis/yt/changeset/cb5c67eed203/
changeset: r3775:cb5c67eed203
branch: yt
user: MatthewTurk
date: 2011-02-26 05:16:21
summary: Updating developer guide to describe using BitBucket
affected #: 1 file (239 bytes)
--- a/doc/how_to_develop_yt.txt Fri Feb 25 10:18:52 2011 -0700
+++ b/doc/how_to_develop_yt.txt Fri Feb 25 23:16:21 2011 -0500
@@ -30,8 +30,9 @@
How To Get The Source Code
--------------------------
-With the yt installation script you should have a copy of Mercurial. You can
-clone the repository like so:
+yt is hosted on BitBucket, and you can see all of the yt repositories at
+http://hg.enzotools.org/ . With the yt installation script you should have a
+copy of Mercurial. You can clone the repository like so:
$ hg clone http://hg.enzotools.org/yt/
@@ -47,6 +48,27 @@
This will rebuild all C modules as well.
+How To Submit Changes
+---------------------
+
+You can submit changes a couple different ways, but the easiest is to use the
+"fork" mechanism on BitBucket. Just go here:
+
+http://hg.enzotools.org/yt/fork
+
+and you're all set, ready to go. You'll have to either clone a new copy of the
+repository or edit .hg/hgrc to point to the location of your new fork, first,
+though.
+
+When you're ready to submit them to the main repository, simply go to:
+
+http://hg.enzotools.org/yt/fork
+
+Make sure you notify "yt_analysis" and put in a little description. That'll
+notify the core developers that you've got something ready to submit, and we
+will review it an (hopefully!) merge it in. If it goes well, you may end up
+with push access to the main repository.
+
How To Read The Source Code
---------------------------
@@ -133,21 +155,3 @@
Once your branch has been merged in, mark it as closed on the wiki page.
-How To Submit Changes
----------------------
-
-If you do not have "push" rights on the primary mercurial repository, set up
-and use the "patchbomb" extension in mercurial to email a bundle of changes to
-the developer mailing list, yt-dev at lists.spacepope.org .
-
-The patchbomb extension is documented here:
-
-http://mercurial.selenic.com/wiki/PatchbombExtension
-
-Please be sure to specify that you wish to send a bundle. This can be
-accomplished by setting up your hgrc to email the yt-dev mailing list and
-executing the command:
-
- $ hg email -b
-
-Be sure to read the output of "hg help email" before doing this.
http://bitbucket.org/yt_analysis/yt/changeset/130af2189c2e/
changeset: r3776:130af2189c2e
branch: stable
user: MatthewTurk
date: 2011-02-26 05:16:21
summary: Updating developer guide to describe using BitBucket
affected #: 1 file (239 bytes)
--- a/doc/how_to_develop_yt.txt Tue Feb 15 16:49:27 2011 -0700
+++ b/doc/how_to_develop_yt.txt Fri Feb 25 23:16:21 2011 -0500
@@ -30,8 +30,9 @@
How To Get The Source Code
--------------------------
-With the yt installation script you should have a copy of Mercurial. You can
-clone the repository like so:
+yt is hosted on BitBucket, and you can see all of the yt repositories at
+http://hg.enzotools.org/ . With the yt installation script you should have a
+copy of Mercurial. You can clone the repository like so:
$ hg clone http://hg.enzotools.org/yt/
@@ -47,6 +48,27 @@
This will rebuild all C modules as well.
+How To Submit Changes
+---------------------
+
+You can submit changes a couple different ways, but the easiest is to use the
+"fork" mechanism on BitBucket. Just go here:
+
+http://hg.enzotools.org/yt/fork
+
+and you're all set, ready to go. You'll have to either clone a new copy of the
+repository or edit .hg/hgrc to point to the location of your new fork, first,
+though.
+
+When you're ready to submit them to the main repository, simply go to:
+
+http://hg.enzotools.org/yt/fork
+
+Make sure you notify "yt_analysis" and put in a little description. That'll
+notify the core developers that you've got something ready to submit, and we
+will review it an (hopefully!) merge it in. If it goes well, you may end up
+with push access to the main repository.
+
How To Read The Source Code
---------------------------
@@ -126,21 +148,3 @@
Once your branch has been merged in, mark it as closed on the wiki page.
-How To Submit Changes
----------------------
-
-If you do not have "push" rights on the primary mercurial repository, set up
-and use the "patchbomb" extension in mercurial to email a bundle of changes to
-the developer mailing list, yt-dev at lists.spacepope.org .
-
-The patchbomb extension is documented here:
-
-http://mercurial.selenic.com/wiki/PatchbombExtension
-
-Please be sure to specify that you wish to send a bundle. This can be
-accomplished by setting up your hgrc to email the yt-dev mailing list and
-executing the command:
-
- $ hg email -b
-
-Be sure to read the output of "hg help email" before doing this.
http://bitbucket.org/yt_analysis/yt/changeset/5a9ff0ccdf4e/
changeset: r3777:5a9ff0ccdf4e
branch: stable
user: MatthewTurk
date: 2011-02-14 17:10:52
summary: Adding a quick note about gcc-4.2
affected #: 1 file (538 bytes)
--- a/doc/install_script.sh Fri Feb 25 23:16:21 2011 -0500
+++ b/doc/install_script.sh Mon Feb 14 11:10:52 2011 -0500
@@ -72,6 +72,7 @@
{
MYHOST=`hostname -s` # just give the short one, not FQDN
MYHOSTLONG=`hostname` # FQDN, for Ranger
+ MYOS=`uname -s` # A guess at the OS
if [ "${MYHOST##kraken}" != "${MYHOST}" ]
then
echo "Looks like you're on Kraken."
@@ -134,6 +135,19 @@
echo " $ module load gcc"
echo
fi
+ if [ "${MYOS##Darwin}" != "${MYOS}" ]
+ then
+ echo "Looks like you're running on Mac OSX."
+ echo
+ echo "NOTE: You may have problems if you are running OSX 10.6 (Snow"
+ echo "Leopard) or newer. If you do, please set the following"
+ echo "environment variables, remove any broken installation tree, and"
+ echo "re-run this script verbatim."
+ echo
+ echo "$ export CC=gcc-4.2"
+ echo "$ export CXX=g++-4.2"
+ echo
+ fi
}
Repository URL: https://bitbucket.org/yt_analysis/yt/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
More information about the yt-svn
mailing list