From: Avery Pennarun <apenwarr@gmail.com>
To: Joey Hess <joey@kitenet.net>
Cc: git@vger.kernel.org
Subject: Re: finding unmerged branches
Date: Thu, 27 Aug 2009 22:22:55 +0000 [thread overview]
Message-ID: <32541b130908271522u1048dcb1h67b79049e46df1ac@mail.gmail.com> (raw)
In-Reply-To: <20090827220241.GA1413@gnu.kitenet.net>
On Thu, Aug 27, 2009 at 10:02 PM, Joey Hess<joey@kitenet.net> wrote:
> What I really want is a way to find remote branches that
> are not merged with any of my local branches (or any origin
> branches). A slow and stupid implementation of that is in the
> attached git-unmerged script, and it weeds the branch list
> down to 68 branches, which are mostly really ones I might
> want to look at.
How about:
gitk $(git for-each-ref --format='%(refname)' 'refs/remotes/'; git
for-each-ref --format='^%(refname)' 'refs/heads/')
You could also replace 'gitk' with 'git log', and mess with the
--pretty=format:whatever parameter.
Have fun,
Avery
next prev parent reply other threads:[~2009-08-27 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 22:02 finding unmerged branches Joey Hess
2009-08-27 22:22 ` Avery Pennarun [this message]
2009-08-28 0:54 ` Joey Hess
2009-08-27 22:35 ` Björn Steinbrink
2009-08-27 23:25 ` Junio C Hamano
2009-08-28 0:44 ` Joey Hess
2009-08-28 2:08 ` Joey Hess
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=32541b130908271522u1048dcb1h67b79049e46df1ac@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
/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).