diff --git a/CHANGELOG.txt b/CHANGELOG.txt
new file mode 100644
index 0000000..4893a25
--- /dev/null
+++ b/CHANGELOG.txt
@@ -0,0 +1,24 @@
+Project Git instructions 6.x-1.x, 2011-04-20
+- Default direction updates
+  * Issue #1128070 by eliza411: Fixed Update Git instructions to include only the basic patch recommendation
+
+Project Git instructions 6.x-1.x, 2011-03-24
+--------------------------------------------
+- Default direction updates
+    * Issue #1080860: Updated commit message directions to explicitly recommend against starting messages with #.
+    * Issue #1092226: Updated command for creating patches from git format-patch to git diff
+    * Issue #1104302: Added directions for applying patches and abandoning local changes.
+
+Project Git instructions 6.x-1.x, 2011-xx-xx
+--------------------------------------------
+-  Default direction updates
+    * Issue #1075982 by helmo, David_Rothstein: Fixed 'Troubleshooting Git clone' link does not appear for projects you maintain.
+
+- Module updates
+    * Issue #1074220 by EclipseGc, helmo: Fixed Numerically Named Branches can result in bad instructions.
+    * Issue #1073394 by drumm: Set project breadcrumb.
+
+Project Git instructions 6.x-1.0, 2011-02-24
+--------------------------------------------
+* Initial release
+* This release marks the transition of drupal.org to Git.
diff --git a/README.txt b/README.txt
new file mode 100644
index 0000000..da6afee
--- /dev/null
+++ b/README.txt
@@ -0,0 +1,10 @@
+Project Git Instructions
+------------------------
+
+This module adds the "Git instructions" tab to certian pages on Drupal.org. This includes modules, themes and installation profiles.
+
+This modules is specifically build for use on drupal.org.
+
+If you are hosting Git repositories yourself and make use of the versioncontrol API modules in drupal then maybe this module can be of service. It has however not been extensively tested on other installations.
+
+See: http://drupal.org/project/project_git_instructions
diff --git a/project_git_instructions.module b/project_git_instructions.module
index b38f1d2..1119d96 100644
--- a/project_git_instructions.module
+++ b/project_git_instructions.module
@@ -34,12 +34,12 @@ function project_git_instructions_nodeapi(&$node, $op, $a3 = NULL, $a4 = NULL) {
   if ($node->type == 'project_project') {
     $src = 'node/' . $node->nid . '/git-instructions';
     if ($op == 'delete') {
-      db_query('DELETE FROM {url_alias} WHERE src = "%s"', $src);
+      db_query("DELETE FROM {url_alias} WHERE src = '%s'", $src);
     }
     elseif (($op == 'update' || $op == 'insert') && !empty($node->project['uri'])) {
       $dst = 'project/' . drupal_urlencode($node->project['uri']) . '/git-instructions';
-      db_query('DELETE FROM {url_alias} WHERE src = "%s"', $src);
-      db_query('INSERT INTO {url_alias} (src, dst) VALUES ("%s", "%s")', $src, $dst);
+      db_query("DELETE FROM {url_alias} WHERE src = '%s'", $src);
+      db_query("INSERT INTO {url_alias} (src, dst) VALUES ('%s', '%s')", $src, $dst);
     }
     elseif ($op == 'view' && $a4) {
       if ($node->project['sandbox']) {
@@ -89,16 +89,17 @@ function project_git_instructions_visibility($node) {
  * @return array Default replacements formatted for t().
  */
 function project_git_instructions_get_defaults($node, $version = NULL) {
-
   global $user;
 
+  project_project_set_breadcrumb($node, TRUE);
+
   $project_url_name = check_plain(drupal_urlencode($node->project['uri'] . '.git'));
 
   // Make the most common set of default replacement variables we can.
   $defaults = array('@project_name' => $project_url_name,
               '@uri' => $node->project['uri'],
               '%title' => $node->title,
-              '@project_fullname' => strtr(drupal_strtolower($node->title), array(' ' => '_'))
+              '@project_fullname' => preg_replace('#\W#', '_', drupal_strtolower($node->title)),
               );
   if ($version) {
     $defaults['@branch'] = check_plain($version);
@@ -141,7 +142,6 @@ function project_git_instructions_get_defaults($node, $version = NULL) {
  * Produce html code for the instructions tab.
  */
 function project_git_instructions_project_tab($node, $version = NULL, $do_nonmaintainer = NULL) {
-
   global $user;
 
   if (empty($node->versioncontrol_project['repo']->vcs)) {
@@ -362,15 +362,22 @@ function project_git_instructions_project_promote_sandbox($project) {
  */
 function project_git_instructions_maintainer() {
   $default = <<<EOT
+<div class="meta">
+<ul>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/CHANGELOG.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
+</div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository in your local environment for the first time:</h3>
+<h3>Setting up this repository in your local environment for the first time</h3>
 If you have just created a project or you already have a local repository, skip this step.
 <div class="codeblock">
 <code>git clone --branch @branch @auth_project_url</code><br /><br />
 <code>cd @uri</code><br />
 </div>
+Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
 <h3>Associating your copy of the repository with your Drupal.org account</h3>
-If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid-no-reply.drupal.org</code>. See <a href="/node/1053134">Manage your Git identity</a> for details.
+If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid.no-reply.drupal.org</code>. See <a href="/node/1022156">Identifying yourself to Git</a> for details.
 <div class="codeblock">
 <code>git config user.email "@email"</code><br />
 </div>
@@ -388,35 +395,67 @@ When you clone the repository you have access to all the branches and tags. The
 <code>git checkout [branchname]</code><br />
 </div>
 
-<h3>Commiting all changes locally</h3>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+<h3>Committing all changes locally</h3>
+After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/52287">Commit messages</a> for details.
 <div class="codeblock">
-<code>git add .</code><br />
+<code>git add -A</code><br />
 <code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code>
 </div>
 <h3>Pushing your code back to the repository on Drupal.org</h3>
 <div class="codeblock">
 <code>git push origin @branch</code><br />
 </div>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
+<div class="codeblock">
+<code>git pull origin @branch</code><br />
+</div>
+
 <h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git checkout -b [description]-[issue-number]</code>
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
-Roll the patch.
+
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git status</code><br />
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>rm  [patchname.patch]</code><br />
+</div>
+
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
+
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
 </div>
+
+<h2>Creating Releases</h2>
+See the <a href="/node/1015226">naming conventions</a> for a complete description of how to name branches and tags so you can create releases.
+<h3>Branch for a dev release</h3>
+This creates and checks out a new branch in one command.
+<div class="codeblock">
+<code>git checkout -b 7.x-1.x</code><br />
+<code>git push origin 7.x-1.x</code><br />
+</div>
+<h3>Tag for a stable release</h3>
+<div class="codeblock">
+<code>git checkout  7.x-1.x</code><br />
+<code>git tag 7.x-1.0</code><br />
+<code>git push origin 7.x-1.0</code><br />
+</div>
+<p>Once you've pushed the properly  formed tag or branch, see <a href="/node/1068944">Creating a project release</a> for directions to actually create the release node.</p>
 EOT;
   return $default;
 }
@@ -426,8 +465,15 @@ EOT;
  */
 function project_git_instructions_nonmaintainer() {
   $default = <<<EOT
+<div class="meta">
+<ul>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
+</div>
+
+
 <h2>One-Time Only</h2>
-<h3>Setting up repository for the first time:</h3>
+<h3>Setting up repository for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @anon_project_url</code><br />
 <code>cd @uri</code><br />
@@ -446,23 +492,40 @@ When you clone the repository you have access to all the branches and tags.  The
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
+<div class="codeblock">
+<code>git pull origin @branch</code><br />
+</div>
+
 <h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git checkout -b [description]-[issue-number]</code>
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
-Roll the patch.
+
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git status</code><br />
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>rm  [patchname.patch]</code><br />
+</div>
+
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
+
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
 </div>
 EOT;
   return $default;
@@ -474,7 +537,7 @@ EOT;
 function project_git_instructions_new_maintainer() {
   $default = <<<EOT
 <h2>Empty Repository</h2>
-<h3>Setting up this repository for the first time:</h3>
+<h3>Setting up this repository for the first time</h3>
 <p>You will be prompted to enter your Drupal.org password after the
 first and last step if you have not uploaded an SSH Key or if your SSH
 key fails. See <a href="/node/1027094">Authenticating with Git on
@@ -511,18 +574,24 @@ EOT;
 
 function project_git_instructions_sandbox_maintainer() {
   $default = <<<EOT
+<div class="meta">
+<ul>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
+</div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository in your local environment for the first time:</h3>
-<p>You will be prompted to enter your Drupal.org password after the
-first step (and any time you make requests from Drupal.org) if you
-have not uploaded an SSH key or if your SSH key fails. See <a
-href="/node/1027094">Authenticate with Git on Drupal.org</a> for
-details.</p>
+<h3>Setting up repository for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @auth_sandbox_url @project_fullname</code><br />
-<br />
 <code>cd @project_fullname</code><br />
 </div>
+Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
+<h3>Associating your copy of the repository with your Drupal.org account</h3>
+If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid-no-reply.drupal.org</code>. See <a href="/node/1022156">Identifying yourself to Git</a> for details.
+<div class="codeblock">
+<code>git config user.email "@email"</code><br />
+</div>
 <h2>Routinely</h2>
 The headings below are not sequential. What you choose to do depends on where you are in your process.
 <h3>Checking your repository status</h3>
@@ -530,63 +599,70 @@ To see what you will commit by running <code>git commit</code> and what you coul
 <div class="codeblock">
 <code>git status</code><br />
 </div>
-
 <h3>Switching to a different branch</h3>
-When you clone the repository you have access to all the branches and tags. The first command shows your choices. The second command makes the switch.  See <a href="/node/1066342">branching and tagging</a> for details.
+When you clone the repository you have access to all the branches and tags.  The first command shows your choices. The second command makes the switch. See <a href="/node/1066342">branching and tagging</a> for details.
 <div class="codeblock">
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
-
-<h3>Committing all changes locally</h3>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
-<div class="codeblock">
-<code>git add .</code><br />
-<code>git commit -m "Message about your changes"</code><br />
-</div>
-<br />
-<p><strong>Note:</strong> When patching in response to an issue from your issue queue, the format for the commit message takes the form
-of:</p>
-<div class="codeblock">
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
-</div>
-<h3>Pushing your code back to the repository on Drupal.org</h3>
-<div class="codeblock">
-<code>git diff origin/@branch</code><br />
-<code>git push origin @branch</code><br />
-</div>
 <h3>Creating a patch</h3>
 For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
 <div class="codeblock">
-<code>git checkout -b [branchname] </code>
+<code>git checkout -b [description]-[issue-number]</code>
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/52287">Commit messages</a> for details.
 <div class="codeblock">
-<code>git add .</code><br />
+<code>git add -A</code><br />
 <code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
 </div>
-
 Roll the patch.
 <div class="codeblock">
+<code>git status</code><br />
 <code>git fetch origin</code><br />
 <code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>git diff origin/@branch  > [description]-[issue-number]-[comment-number].patch</code><br />
 </div>
+
+<h3>Applying a patch</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch and that it is up-to-date using the following commands:
+<div class="codeblock">
+<code>git checkout --track origin/@branch</code><br />
+<code>git pull origin @branch</code><br />
+</div>
+
+Next, download the patch to your working directory to apply it. There are many variables involved in applying patches, so if the following command doesn't work for you, see <a href="/patch/apply">Applying patches</a> for more detail.</p>
+<div class="codeblock"><code>git apply [patch.name]</code><br /></div>
+Finally, remove the patch file:
+<div class="codeblock"><code>rm  [patch.name]</code><br /></div>
+
+<h3>Abandoning your local changes</h3>
+<p>
+Abandon changes to a specific file: <br />
+<div class="codeblock"><code>git checkout [filename]</code></div>
+</p><p>
+Abandon changes to the whole working tree: <br />
+<div class="codeblock"><code>git reset --hard</code></div>
+</p>
 EOT;
   return $default;
 }
 
 function project_git_instructions_sandbox_nonmaintainer() {
   $default = <<<EOT
+<div class="meta">
+<ul>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
+</div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository locally for the first time:</h3>
+<h3>Setting up this repository locally for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @anon_sandbox_url @project_fullname</code><br />
 <code>cd @project_fullname</code>
 </div>
 Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
+
 <h2>Routinely</h2>
 The headings below are not sequential. What you choose to do depends on where you are in your process.
 <h3>Checking your repository status</h3>
@@ -594,30 +670,46 @@ To see what you will commit by running <code>git commit</code> and what you coul
 <div class="codeblock">
 <code>git status</code><br />
 </div>
-
 <h3>Switching to a different branch</h3>
 When you clone the repository you have access to all the branches and tags. The first command shows your choices. The second command makes the switch.  See <a href="/node/1066342">branching and tagging</a> for details.
 <div class="codeblock">
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
+<div class="codeblock">
+<code>git pull origin @branch</code><br />
+</div>
+
 <h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git checkout -b [branchname] </code>
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git add .</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
 
-Roll the patch.
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>rm  [patchname.patch]</code><br />
+</div>
+
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
+
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
 </div>
 EOT;
   return $default;
@@ -626,7 +718,7 @@ EOT;
 function project_git_instructions_sandbox_new_maintainer() {
   $default = <<<EOT
 <h2>Empty Sandbox Repository</h2>
-<h3>Setting up this repository for the first time:</h3>
+<h3>Setting up this repository for the first time</h3>
 <p>You will be prompted to enter your Drupal.org password after the last step (and any time you make requests from Drupal.org) if you have not uploaded an SSH key or if your SSH key fails. See <a href="/node/1027094">Authenticate with Git on Drupal.org</a> for details.</p>
 <div class="codeblock">
 <code>mkdir @project_fullname</code><br /><br />
