From: E R <pc88mxer@gmail.com>
To: "Nathan W. Panike" <nathan.panike@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: help with git query
Date: Mon, 13 Apr 2009 15:57:26 -0500 [thread overview]
Message-ID: <3a69fa7c0904131357w5ef6b8feu7aac503fdcc4486c@mail.gmail.com> (raw)
In-Reply-To: <d77df1110904131331p24f52220o74c401c97fbb904d@mail.gmail.com>
Thanks - that's very helpful.
For the second question, is it possible to find the commit that
represents the merge in the master branch?
i.e.
git merge-base XXX master
returns the commit in branch XXX that got merged into master. I'd like
to also find the commit that represents the merge in master.
On Mon, Apr 13, 2009 at 3:31 PM, Nathan W. Panike
<nathan.panike@gmail.com> wrote:
> On Mon, Apr 13, 2009 at 1:51 PM, E R <pc88mxer@gmail.com> wrote:
>> Hi,
>>
>> I'd like to generate the following report from git:
>>
>> for each branch:
>> - info about the latest commit on that branch (date and time, message, etc.)
>
> Depending on what you want to do---from a bash shell, you could do:
>
> for i in $(git branch -a | cut -b3-); do echo $i; git show -s $i; echo; done
>
>> - info about the last time it was merged into master
>
> for i in $(git branch -a | cut -b3-); do echo $i; git show -s $(git
> merge-base $i master); echo; done
>>
>> What commands can I run to figure this out? I think I can figure out
>> the first one - it's the second one I'm having trouble with.
>>
>> And if it would easier to do it from the C API (or something like the
>> perl Git::PurePerl module) I'd be interested in knowing that, too.
>>
>> Thanks,
>> ER
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
next prev parent reply other threads:[~2009-04-13 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 18:51 help with git query E R
2009-04-13 20:31 ` Nathan W. Panike
2009-04-13 20:57 ` E R [this message]
2009-04-13 22:33 ` Nathan W. Panike
2009-04-14 5:46 ` Jeff King
2009-04-14 6:26 ` Björn Steinbrink
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=3a69fa7c0904131357w5ef6b8feu7aac503fdcc4486c@mail.gmail.com \
--to=pc88mxer@gmail.com \
--cc=git@vger.kernel.org \
--cc=nathan.panike@gmail.com \
/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).