* Getting the "message" given a branch designation and conversely
@ 2016-08-14 14:58 norm
2016-08-14 17:32 ` Philip Oakley
2016-08-15 12:28 ` Jeff King
0 siblings, 2 replies; 4+ messages in thread
From: norm @ 2016-08-14 14:58 UTC (permalink / raw)
To: git; +Cc: norm
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Getting the "message" given a branch designation and conversely
2016-08-14 14:58 Getting the "message" given a branch designation and conversely norm
@ 2016-08-14 17:32 ` Philip Oakley
2016-08-15 12:28 ` Jeff King
1 sibling, 0 replies; 4+ messages in thread
From: Philip Oakley @ 2016-08-14 17:32 UTC (permalink / raw)
To: Norman Shapiro, git; +Cc: norm
From: <norm@dad.org>
>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^!'
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Getting the "message" given a branch designation and conversely
2016-08-14 14:58 Getting the "message" given a branch designation and conversely norm
2016-08-14 17:32 ` Philip Oakley
@ 2016-08-15 12:28 ` Jeff King
2016-08-24 14:39 ` Jakub Narębski
1 sibling, 1 reply; 4+ messages in thread
From: Jeff King @ 2016-08-15 12:28 UTC (permalink / raw)
To: norm; +Cc: git
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Getting the "message" given a branch designation and conversely
2016-08-15 12:28 ` Jeff King
@ 2016-08-24 14:39 ` Jakub Narębski
0 siblings, 0 replies; 4+ messages in thread
From: Jakub Narębski @ 2016-08-24 14:39 UTC (permalink / raw)
To: Jeff King, norm; +Cc: git
W dniu 15.08.2016 o 14:28, Jeff King pisze:
> 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).
>> 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)).
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-08-24 14:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-14 14:58 Getting the "message" given a branch designation and conversely norm
2016-08-14 17:32 ` Philip Oakley
2016-08-15 12:28 ` Jeff King
2016-08-24 14:39 ` Jakub Narębski
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).