From: Michael J Gruber <git@drmicha.warpmail.net>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] revisions.txt: language improvements
Date: Thu, 31 Mar 2011 14:19:07 +0200 [thread overview]
Message-ID: <4D94713B.5090603@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTikofGHcJtHMAqhAM7ofD=f2jybPAiJTnV=4ciu7@mail.gmail.com>
Bert Wesarg venit, vidit, dixit 31.03.2011 14:19:
> On Thu, Mar 31, 2011 at 13:03, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
>> ---
>> Documentation/revisions.txt | 68 +++++++++++++++++++++---------------------
>> 1 files changed, 34 insertions(+), 34 deletions(-)
>>
>> diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
>> index fa399df..288fa6e 100644
>> --- a/Documentation/revisions.txt
>> +++ b/Documentation/revisions.txt
>> @@ -27,30 +27,30 @@ blobs contained in a commit.
>> When ambiguous, a '<name>' is disambiguated by taking the
>> first match in the following rules:
>>
>> - . if '$GIT_DIR/<name>' exists, that is what you mean (this is usually
>> + . If '$GIT_DIR/<name>' exists, that is what you mean (this is usually
>> useful only for 'HEAD', 'FETCH_HEAD', 'ORIG_HEAD', 'MERGE_HEAD'
>> and 'CHERRY_PICK_HEAD');
>>
>> - . otherwise, 'refs/<name>' if exists;
>> + . otherwise, 'refs/<name>' if it exists;
>>
>> - . otherwise, 'refs/tags/<refname>' if exists;
>> + . otherwise, 'refs/tags/<refname>' if it exists;
>>
>> - . otherwise, 'refs/heads/<name>' if exists;
>> + . otherwise, 'refs/heads/<name>' if it exists;
>>
>> - . otherwise, 'refs/remotes/<name>' if exists;
>> + . otherwise, 'refs/remotes/<name>' if it exists;
>>
>> - . otherwise, 'refs/remotes/<name>/HEAD' if exists.
>> + . otherwise, 'refs/remotes/<name>/HEAD' it if exists.
>
> s/it if/if it/
Uh, thanks. Waiting for more feedback before a re-roll.
>
>> +
>> -'HEAD' names the commit your changes in the working tree is based on.
>> -'FETCH_HEAD' records the branch you fetched from a remote repository
>> +'HEAD' names the commit on which you based the changes in the working tree.
>> +'FETCH_HEAD' records the branch which you fetched from a remote repository
>> with your last `git fetch` invocation.
>> -'ORIG_HEAD' is created by commands that moves your 'HEAD' in a drastic
>> +'ORIG_HEAD' is created by commands that move 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.
>> -'MERGE_HEAD' records the commit(s) you are merging into your branch
>> +you can easily change the tip of the branch back to the state before you ran
>> +them.
>> +'MERGE_HEAD' records the commit(s) which you are merging into your branch
>> when you run `git merge`.
>> -'CHERRY_PICK_HEAD' records the commit you are cherry-picking
>> +'CHERRY_PICK_HEAD' records the commit which you are cherry-picking
>> when you run `git cherry-pick`.
>> +
>> Note that any of the 'refs/*' cases above may come either from
next prev parent reply other threads:[~2011-03-31 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 11:03 [PATCH 0/3] revisions.txt improvements Michael J Gruber
2011-03-31 11:03 ` [PATCH 1/3] revisions.txt: consistent use of quotes Michael J Gruber
2011-03-31 11:03 ` [PATCH 2/3] revisions.txt: structure with a labelled list Michael J Gruber
2011-03-31 21:46 ` Jakub Narebski
2011-04-01 7:01 ` Michael J Gruber
2011-03-31 11:03 ` [PATCH 3/3] revisions.txt: language improvements Michael J Gruber
2011-03-31 12:19 ` Bert Wesarg
2011-03-31 12:19 ` Michael J Gruber [this message]
2011-04-01 9:27 ` [PATCHv2 0/3] revisions.txt improvements Michael J Gruber
2011-04-01 9:27 ` [PATCH 1/3] revisions.txt: consistent use of quotes Michael J Gruber
2011-04-01 9:27 ` [PATCHv2 2/3] revisions.txt: structure with a labelled list Michael J Gruber
2011-04-03 19:01 ` Junio C Hamano
2011-04-01 9:27 ` [PATCHv2 3/3] revisions.txt: language improvements Michael J Gruber
2011-04-01 22:05 ` Junio C Hamano
2011-04-03 13:05 ` Michael J Gruber
2011-04-04 15:27 ` [PATCHv3 0/3] revisions.txt improvements Michael J Gruber
2011-04-04 15:27 ` [PATCHv3 1/3] revisions.txt: consistent use of quotes Michael J Gruber
2011-04-04 15:27 ` [PATCHv3 2/3] revisions.txt: structure with a labelled list Michael J Gruber
2011-04-04 15:27 ` [PATCHv3 3/3] revisions.txt: language improvements Michael J Gruber
2011-04-04 18:18 ` [PATCHv3 0/3] revisions.txt improvements Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D94713B.5090603@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).