Recent changes to Submissions

Submissions modified by Code Guru

Code Guru — Sun, 11 Aug 2013 23:41:14 -0000

Submissions modified by Code Guru

Code Guru — Sun, 11 Aug 2013 23:40:59 -0000

--- v10
+++ v11
@@ -2,7 +2,7 @@
 ==================

-To submit changes to BBCT, you first need to clone the git repository. You can find instructions at [Getting Started]. When you have cloned the repository, be sure to pull the `devel` branch and create a new branch for your own work. Make small, cohesive commits for the changes you want to submit. When you are ready to submit your changes, you need to make a patch and submit it to the mailing list. (The following instructions use `$BBCT_HOME` to refer to the base directory where you cloned the git repository.)
+To submit changes to BBCT, you first need to clone the git repository. You can find instructions at [Getting Started]. When you have cloned the repository, be sure to pull the `devel` branch and create a new branch for your own work. Make small, cohesive commits for the changes you want to submit. (See [Git Commit Message Guidelines].) When you are ready to submit your changes, you need to make a patch and submit it to the mailing list. (The following instructions use `$BBCT_HOME` to refer to the base directory where you cloned the git repository.)

 1. Create a patch with Git:

Submissions modified by Code Guru

Code Guru — Wed, 31 Jul 2013 00:43:35 -0000

--- v9
+++ v10
@@ -22,7 +22,7 @@

     * Log into your email account.

-    * Create a new email to [bbct-list@lists.sourceforge.net][3].
+    * Create a new email to [bbct-list@lists.sourceforge.net][3] and start the Subject field with "Code Review:" followed by a short description of the changes made in the patch which you are submitting.

     * Copy and paste the contents of  a single `.patch` file in the body of the email in order to facilitate inline comments to the proposed changes.

Submissions modified by Code Guru

Code Guru — Wed, 31 Jul 2013 00:16:59 -0000

--- v8
+++ v9
@@ -24,9 +24,11 @@

     * Create a new email to [bbct-list@lists.sourceforge.net][3].

-    * Include the `.patch` files in the body of the email in order to facilitate inline comments to the proposed changes.
+    * Copy and paste the contents of  a single `.patch` file in the body of the email in order to facilitate inline comments to the proposed changes.

-    * Attach the `.patch` files from `$BBCT_HOME/patch`.
+    * Attach the `.patch` file from `$BBCT_HOME/patch`.
+
+    * Repeate steps 3 through 5 as needed for each `.patch` file. (There should be one `.patch` file per commit in the change set.)

 [1]:https://sourceforge.net/p/bbct/bbct-list/
 [2]:https://lists.sourceforge.net/lists/listinfo/bbct-list

Submissions modified by Code Guru

Code Guru — Wed, 31 Jul 2013 00:14:00 -0000

--- v7
+++ v8
@@ -22,7 +22,11 @@

     * Log into your email account.

-    * Create a new email to [bbct-list@lists.sourceforge.net][3] and attach the `.patch` files from `$BBCT_HOME/patch`.
+    * Create a new email to [bbct-list@lists.sourceforge.net][3].
+
+    * Include the `.patch` files in the body of the email in order to facilitate inline comments to the proposed changes.
+
+    * Attach the `.patch` files from `$BBCT_HOME/patch`.

 [1]:https://sourceforge.net/p/bbct/bbct-list/
 [2]:https://lists.sourceforge.net/lists/listinfo/bbct-list

Submissions modified by Code Guru

Code Guru — Wed, 31 Jul 2013 00:11:56 -0000

Submissions modified by Code Guru

Code Guru — Mon, 22 Jul 2013 23:45:23 -0000

--- v5
+++ v6
@@ -8,13 +8,13 @@

     1. In `$BBCT_HOME`, create a subdirectory named `patch`.

-    * Pull the most recent version of the `devel` branch (e.g. with `git pull devel` from the command-line).
+    * Pull the most recent version of the `devel` branch (e.g. with '`git pull devel`' from the command-line).

-    * Checkout the branch containing your work (e.g. with `git checkout`).
+    * Checkout the branch containing your work (e.g. with '`git checkout`').

-    * Rebase your work onto `devel` (e.g. with `git rebase devel`).
+    * Rebase your work onto `devel` (e.g. with '`git rebase devel`').

-    * Create the patch series for your work. From a command prompt, run `cd $BBCT_HOME` and `git format-patch -o patch devel..HEAD`.
+    * Create the patch series for your work. From a command prompt, run '`cd $BBCT_HOME`' and '`git format-patch -o patch devel..HEAD`'.

 * Email the patch files to [bbct-list][1].

Submissions modified by Code Guru

Code Guru — Mon, 22 Jul 2013 23:44:37 -0000

--- v4
+++ v5
@@ -6,7 +6,7 @@

 1. Create a patch with Git:

-    a. In `$BBCT_HOME`, create a subdirectory named `patch`.
+    1. In `$BBCT_HOME`, create a subdirectory named `patch`.

     * Pull the most recent version of the `devel` branch (e.g. with `git pull devel` from the command-line).

@@ -18,7 +18,7 @@

 * Email the patch files to [bbct-list][1].

-    * If you have not yet, [join the BBCT mailing list][2].
+    1. If you have not yet, [join the BBCT mailing list][2].

     * Log into your email account.

Submissions modified by Code Guru

Code Guru — Mon, 22 Jul 2013 23:44:18 -0000

--- v3
+++ v4
@@ -6,7 +6,7 @@

 1. Create a patch with Git:

-    * In `$BBCT_HOME`, create a subdirectory named `patch`.
+    a. In `$BBCT_HOME`, create a subdirectory named `patch`.

     * Pull the most recent version of the `devel` branch (e.g. with `git pull devel` from the command-line).

Submissions modified by Code Guru

Code Guru — Mon, 22 Jul 2013 23:44:05 -0000

--- v2
+++ v3
@@ -16,7 +16,7 @@

     * Create the patch series for your work. From a command prompt, run `cd $BBCT_HOME` and `git format-patch -o patch devel..HEAD`.

-2. Email the patch files to [bbct-list][1].
+* Email the patch files to [bbct-list][1].

     * If you have not yet, [join the BBCT mailing list][2].