Re: [FIXED PATCH] Make rebase save ORIG_HEAD if changing current branch

From: Jay Soffian <jaysoffian@gmail.com>
Date: Jul 8, 2008, 03:28 UTC
Message-ID: <76718490807072028o7e0661a8r6d118cc91dc5e625@mail.gmail.com>
In-Reply-To: <7vod591hlp.fsf@gitster.siamese.dyndns.org>

On Mon, Jul 7, 2008 at 5:58 PM, Junio C Hamano <gitster@pobox.com> wrote:

> +HEAD names the commit your changes in the working tree is based on.

How about:

"HEAD names the commit your working tree is based on. This is the tip of the checked out branch, unless HEAD is detached. (HEAD is said to be detached if a commit is checked out which is not the tip of any branch.)"

> +FETCH_HEAD records the branch you fetched from a remote repository
> +with your last 'git-fetch' invocation.

consistency w/above: s/records/names/

> +ORIG_HEAD is created by commands that moves your HEAD in a drastic
> +way, to record the position of the HEAD before their operation, so that
> +you can change the tip of the branch back to the state before you ran
> +them easily.

s/moves/move/; s/can change/can easily change/; s/them easily./them./;

But maybe this reads better:

ORIG_HEAD is created by commands that move HEAD in a drastic way to record the position of HEAD before their operation, so that the branch can easily be reset back to its prior state.

> +MERGE_HEAD records the commit(s) you are merging into your branch
> +when you run 'git-merge'.

So it's the "<remote>" arg or args mentioned in the git-merge man page?

j.