threads / discuss / 43840

Getting the "message" given a branch designation and conversely

Subject: Getting the "message" given a branch designation and conversely

## tl;dr

4 messages between Aug 14, 2016 and Aug 24, 2016.

replies: 3people: 4as markdown or json

norm@dad.org· Aug 14, 2016, 14:58 UTC · lore
I am learning how to use git. I would like to know how:

Given a branch's designation, such as "master~4", how can I see the message I furnished when I created the branch using "git commit"?

Conversely, given the message I furnished to "git commit", when I created a branch, how can I see the branch's designation?

Context:
    Operating System: Red Hat Enterprise Linux Workstation release 6.8
    git version: 1.7.1
Thank you, very much.
    Norman Shapiro
Philip Oakley· Aug 14, 2016, 17:32 UTC · re: norm@dad.org · lore

Re: Getting the "message" given a branch designation and conversely

From: <norm@dad.org>
Show 20 quoted lines
>I am learning how to use git. I would like to know how:
>
> Given a branch's designation, such as "master~4", how can I see the 
> message I
> furnished when I created the branch using "git commit"?
>
> Conversely, given the message I furnished to "git commit", when I created 
> a
> branch, how can I see the branch's designation?
>
> Context:
>
>    Operating System: Red Hat Enterprise Linux Workstation release 6.8
>
>    git version: 1.7.1
>
> Thank you, very much.
>
>    Norman Shapiro
> --
Norman,

To see the commit message try 'git log'. You will need a revision range, so try 'git help revisions' to set a guide about all the different ways you can spell that. While at it, it's worth 'git help glossary' just to understand some of the terminology.

-- Philip 'git log HEAD~4^!'

Jeff King· Aug 15, 2016, 12:28 UTC · re: norm@dad.org · lore

Re: Getting the "message" given a branch designation and conversely

On Sun, Aug 14, 2016 at 07:58:14AM -0700, norm@dad.org wrote:
> I am learning how to use git. I would like to know how:
> 
> Given a branch's designation, such as "master~4", how can I see the message I
> furnished when I created the branch using "git commit"?

Somebody already pointed you at "git log", which is the right tool for looking at commit messages (or perhaps "git show" if you only want to see a single entry).

> Conversely, given the message I furnished to "git commit", when I created a
> branch, how can I see the branch's designation?

Try "git log --grep=some.regex" to find a particular commit. Usually we refer to commits by their sha1 id, which will be shown by git-log. However, you can use git-describe to generate a name for any commit that is based on traversing from a tag. Try:

  git describe --contains --all <sha1>

for example. Using "--all" tells git to consider names based on branches as well as tags. Using "--contains" will generate a name based on traversing backwards from the tags and branches (like "master~4") rather than basing the name on a tag that you build off of.

-Peff
Jakub Narębski· Aug 24, 2016, 14:39 UTC · re: Jeff King · lore

Re: Getting the "message" given a branch designation and conversely

W dniu 15.08.2016 o 14:28, Jeff King pisze:
Show 10 quoted lines
> On Sun, Aug 14, 2016 at 07:58:14AM -0700, norm@dad.org wrote:
> 
>> I am learning how to use git. I would like to know how:
>>
>> Given a branch's designation, such as "master~4", how can I see the message I
>> furnished when I created the branch using "git commit"?
> 
> Somebody already pointed you at "git log", which is the right tool for
> looking at commit messages (or perhaps "git show" if you only want to
> see a single entry).

I think you would want "git log -1 master~4" or "git show master~4" to see the commit message of a single commit (without diff).

Show 5 quoted lines
>> Conversely, given the message I furnished to "git commit", when I created a
>> branch, how can I see the branch's designation?
> 
> Try "git log --grep=some.regex" to find a particular commit. Usually we
> refer to commits by their sha1 id, which will be shown by git-log.

There is also :/<search> and <rev>^{/<search>} syntax, if you want composability (see gitrevisions(7)).

Show 9 quoted lines
> However, you can use git-describe to generate a name for any commit that
> is based on traversing from a tag. Try:
> 
>   git describe --contains --all <sha1>
> 
> for example. Using "--all" tells git to consider names based on branches
> as well as tags. Using "--contains" will generate a name based on
> traversing backwards from the tags and branches (like "master~4") rather
> than basing the name on a tag that you build off of.
The "git describe --contains" is interface to "git name-rev" plumbing
-- 
Jakub Narębski

← back to recent threads