suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update ubuntu instructions, remove references to "me".

Browse Source
This commit is contained in:
Eli Barzilay 2010-10-02 17:43:18 -04:00
parent 9a4b2d2023
commit 7d82210e29
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
collects/meta/web/stubs/git.rkt
View File

@ -151,6 +151,7 @@
@ul*{ @ul*{
@~ Ubuntu: @~ Ubuntu:
@pre{sudo add-apt-repository ppa:git-core/ppa @pre{sudo add-apt-repository ppa:git-core/ppa
sudo apt-get update
sudo apt-get install git-core} sudo apt-get install git-core}
@~ OSX using macports: @~ OSX using macports:
@pre{sudo port selfupdate @pre{sudo port selfupdate
@ -210,8 +211,8 @@
server, is via ssh. (Access is controlled via a tool called “gitolite” — server, is via ssh. (Access is controlled via a tool called “gitolite” —
more on this below.) The username and hostname of the server is more on this below.) The username and hostname of the server is
"git@at-git-racket" — and you should be able to connect to this account using "git@at-git-racket" — and you should be able to connect to this account using
the ssh identity key that corresponds to the public key that you gave me. To the ssh identity key that corresponds to the public key that you use with the
try it, run git server. To try it, run
@pre{ssh git@at-git-racket} @pre{ssh git@at-git-racket}
and the server (gitolite, actually) should reply with information about your and the server (gitolite, actually) should reply with information about your
current permissions. The exact details of this is not important for now, current permissions. The exact details of this is not important for now,
@ -2449,8 +2450,8 @@
@pre{git push my-fork :my-branch} @pre{git push my-fork :my-branch}
Using an empty branch name for the local branch that you push is the way to Using an empty branch name for the local branch that you push is the way to
delete remote branches. (As with local branches, this might lead to losing delete remote branches. (As with local branches, this might lead to losing
commits, so be careful. If you make a mistake, let me know, since it is commits, so be careful. As always, git has a few safety mechanisms in
likely easy to fix.)} place, so even if did this by mistake, it is very likely recoverable.)}
@h3{Using a clone of your private repository, pushing changes to the public @h3{Using a clone of your private repository, pushing changes to the public
one:} one:}
@ol*{ @ol*{