From: Sean Kelley <sean.v.kelley@gmail.com>
Date: Wed, 22 Nov 2006 14:28:58 GMT
Subject: Re: Stupid Git question
Message-ID: <89b129c60611220628l59e305b8h4d2196f7cf6498d4@mail.gmail.com>
In-Reply-To: <ejvs65$vo8$1@sea.gmane.org>

On 11/21/06, Jakub Narebski <jnareb@gmail.com> wrote:
> Sean Kelley wrote:
>
> > git checkout origin
>
> It should be "git checkout master". You shouldn't do work on tracking
> branches like origin branch.
>
> > git pull . fm-modulator
> >
> > git push origin
>
> Here origin means origin remote (repository). Check out what you have in
> remotes/origin, or in [remote "origin"] section in git config.


Thanks!  One more question.  It appears that the problem that I am
having is that people are comitting to origin and should be committing
to master.  Perhaps the names can be confusing.  One suggestion made
is that we give a branch on the remote server a more meaningful name.

If on my remote server I have:

  /data/git/kernel/mh.git

How do I add a branch to the remote repository that is visible to all
team members.  It seems like the git checkout -b commands just create
local topic branches.

So I would have something like:

git clone git+ssh://git.example.com/data/git/kernel/mh.git kernel
cd kernel
git checkout Project
git checkout -b fm-modulator
edit/add/commit changes...

git checkout Project
git pull . fm-modulator
git push origin Project

So how do I create this Project branch on the remote repository such
that it is visible to all?  Do I log onto the remove server and do it
manually?  If so, how is that done?

Thanks!

Sean

> --
> Jakub Narebski
> Warsaw, Poland
> ShadeHawk on #git
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


--