Three minutes ago, Stefan Schmiedl wrote:
> Assuming that you have your changes committed to the repository on
> machine A, you could run the following on B:
>
> git clone m...@a:repo-path
>
> This should get you the contents of A onto B and also configure B to
> use A as "origin", so that a "git push" on B would push the changes
> to A. Also "git pull" now tracks the repo at A.
>
> To get to the "main" repo, you could use
>
> git remote add main m...@main-repo:repo-path
>
> and then use "git pull main" and "git push main" to access that one.
Actually, assuming that Robby wants to push from either place to the
main repository, having the default be the local one is something that
will be easy to trip over.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
