From 9b898149c1dec8b7c2c59dca438d58bdacde3c29 Mon Sep 17 00:00:00 2001
From: Michael Marsh <mmarsh@cs.umd.edu>
Date: Wed, 14 Aug 2019 12:24:37 -0400
Subject: [PATCH] updated for server/process changes
---
README | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/README b/README
index ffdb905..facf462 100644
--- a/README
+++ b/README
@@ -244,7 +244,7 @@ clone [may require Internet access]
The latter is what we'll mostly be using in this course. More specifically:
- git clone git@gizmonic.cs.umd.edu:repo_name
+ git clone git@gitlab.cs.umd.edu:repo_name
init --bare
-----------
@@ -487,11 +487,11 @@ remote
git push other master
- Congratulations! You've just created a fork! We're going to do this
- frequently. Your VM has a directory ~/tools with a script get-assignment
- that automates this process. Take a look at this, and see how the commands
- match with what we've just done manually. Note that there's some magic here
- that's specific to the gitolite server on gizmonic.cs.umd.edu.
+ Congratulations! You've just created a fork! We're going to do
+ this frequently. Luckily for you, we've mostly automated the
+ forking process, so a script we run will fork our (invisible to
+ you) project repositories into a new project to which you have
+ access.
branch
------
--
GitLab