Re: pushing changes to a remote branch

From: Jan Hudec <bulb@ucw.cz>
Date: Jul 11, 2007, 19:31 UTC
Message-ID: <20070711193152.GC3069@efreet.light.src>
In-Reply-To: <844FC382-DFB3-4762-93C2-6512612136AC@silverinsanity.com>

On Tue, Jul 10, 2007 at 14:10:01 -0400, Brian Gernhardt wrote:

Show 9 quoted lines

> Indeed, in master, git outputs a hint to that when you checkout the remote 
> branch.
>
>   $ git checkout origin/master
>   Note: moving to "origin/master" which isn't a local branch
>   If you want to create a new branch from this checkout, you may do so
>   (now or later) by using -b with the checkout command again. Example:
>     git checkout -b <new_branch_name>
>   HEAD is now at f4855d4... 1

The problem of this warning is, that it does not actually say anything about detached and that potential commit won't update the ref being checked out.

> Perhaps git-commit should also also output a warning?  "Commit made on 
> detached HEAD.  Use "git branch <new_branch_name>" to save your commit"?  
> That's bad wording, but the idea is there.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>