diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-11-05 18:03:27 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-11-05 18:03:27 +0000 |
| commit | a089a2ee0ea71dfed1b2c3d00380884e5dcbd210 (patch) | |
| tree | a885617e1a01afe66ebe38d9a55dce8c5218978b | |
| parent | 5694d0a94805b4ab35465397c5f30bc09dbab984 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Purge_a_remote/comment_3_63e0280273b816fa4b837724e102f813._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Purge_a_remote/comment_3_63e0280273b816fa4b837724e102f813._comment b/doc/forum/Purge_a_remote/comment_3_63e0280273b816fa4b837724e102f813._comment new file mode 100644 index 000000000..621bda508 --- /dev/null +++ b/doc/forum/Purge_a_remote/comment_3_63e0280273b816fa4b837724e102f813._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 3" + date="2013-11-05T18:03:26Z" + content=""" +Hmm well, it's true that deleting a repository does not clean out any git remotes that other repositories might have configured using it, and the uuid of the old remote is cached in there. This is only a problem if you put back another repository in the same location as the old one. `git remote remove` should clean that up for you. +"""]] |