John Mandereau wrote:
> There is really no risk of collision with a previous
> existing repository: if there was one, 'git init' would
> barf.
Except that once I designate a remote branch `origin', I
need to name the other branch something else? My
understanding is hazy, but from the build directory of my
`master' repo, adding the lilypond/translation branch as in
CG 1.1.4 returns `fatal: remote origin already exists.' The
whole procedure in context follows below; what's the right
way to do it?
Thanks
- Mark
$ mkdir lilypond; cd lilypond
$ git init
Initialized empty Git repository in /home/owner/lilypond/
$ git remote add -ft master -m master origin \
git://git.sv.gnu.org/lilypond.git/
Updating origin...
etc.
$ git checkout -b master origin/master
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of origin/master.
Branch master set up to track remote branch master from
origin.
Already on 'master'
$ git remote add -ft lilypond/translation -m \
lilypond/translation origin \
git://git.sv.gnu.org/lilypond.git/
fatal: remote origin already exists.
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
