Changes between Version 45 and Version 46 of CollaborateOnGithub

Timestamp:

Aug 14, 2011, 10:25:47 PM (13 years ago)

Author:

anonymous

Comment:

DELETING SPAM. WHY DON'T YOU HAVE A CAPTCHA????????

CollaborateOnGithub

@@ -38 +38 @@
 (From http://cheat.errtheblog.com/s/git)
 
-Tell `git branch` and `git checkout` to setup new branches so that `git pull` will [http://www.diamondlinks.net/ link building] appropriately merge from that remote branch. Without this, you will have to add `--track` to your branch command or manually merge remote tracking branches with `fetch` and then `merge`
+Tell `git branch` and `git checkout` to setup new branches so that `git pull` will appropriately merge from that remote branch. Without this, you will have to add `--track` to your branch command or manually merge remote tracking branches with `fetch` and then `merge`
 {{{
 git config branch.autosetupmerge true
@@ -81 +81 @@
 === Working on a task ===
 
-'''Goal''': keep the changes self-contained, create and update patches suitable for [http://www.truckaccidentlawyersource.com/ truck accident lawyer] attaching to [http://code.djangoproject.com/simpleticket tickets in Django trac].
+'''Goal''': keep the changes self-contained, create and update patches suitable for attaching to [http://code.djangoproject.com/simpleticket tickets in Django trac].
 
  1. Create a branch from master
@@ -189 +189 @@
 should alleviate the problem and `git push` should work again.
 
-Generally, `non-fast forward` means that the local history differs from the [http://www.mycaal.com/ loan modification] remote history and pushing would change remote history.
+Generally, `non-fast forward` means that the local history differs from the remote history and pushing would change remote history.
 Although rewriting history may wreak havoc if someone has forked your repository after the changed point, it is sometimes necessary.