From 2c3dd683f1cdc7b2239e22ff49606b4691d0f9a4 Mon Sep 17 00:00:00 2001 From: Ben Lynn Date: Tue, 5 Aug 2008 20:51:50 -0700 Subject: [PATCH] Removed confusing push paragraph. --- clone.txt | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/clone.txt b/clone.txt index 1a94e88..031db33 100644 --- a/clone.txt +++ b/clone.txt @@ -19,16 +19,6 @@ to create a second copy of the files and Git repository. From now on, will pull in the state of the files on the other computer into the one you're working on. If you've recently made conflicting edits in the same file, Git will let you know and you should commit again after resolving them. -Pushing is also possible. If you have not committed any changes on the other computer, you may type - - $ git push other.computer:/path/to/files - -to push the current state to the other computer. Next time you're logged in to the other computer, run - - $ git checkout HEAD . - -to update the files before working on them, though this won't work if you have uncommitted changes. Because more work is required, I prefer sticking to pulls for this use case. - === Classic Source Control === Initialize a Git repository for your files: -- 2.11.4.GIT