diff options
| author | tekkub <tekkub@gmail.com> | 2010-02-01 16:49:07 -0700 |
|---|---|---|
| committer | tekkub <tekkub@gmail.com> | 2010-02-01 16:49:07 -0700 |
| commit | 96d14156b3da0a5e1c08f5069fa03c78d631d0a4 (patch) | |
| tree | bbbb06b437f56bcaf709c4b5d12b6c6569376dcf | |
| parent | 7d866868f3c7e01e933692597e862f5364b5353e (diff) | |
Fix a rogue [1] in rebase guide... rename it for ordering
| -rwxr-xr-x[-rw-r--r--] | _posts/2010-01-29-rebase.markdown (renamed from _posts/2010-01-28-rebase.markdown) | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2010-01-28-rebase.markdown b/_posts/2010-01-29-rebase.markdown index c3aac53..11e900a 100644..100755 --- a/_posts/2010-01-28-rebase.markdown +++ b/_posts/2010-01-29-rebase.markdown @@ -13,7 +13,7 @@ So, you've cloned a repository, and hacked away at it; separated it into logical So you send your patch series, or publish your branch, and ask for a pull, but a quick review reveals that there are some errors in these patches! -Now, the maintainer may send these patches back to you, and ask you to fix these, this guide shows several ways on how this can be accomplished[1]. +Now, the maintainer may send these patches back to you, and ask you to fix these, this guide shows several ways on how this can be accomplished. Before you start, make sure you have a clean working tree (i.e. no modified files). |