From: Cheng Renquan <crquan@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [RFC] git branch --status ?
Date: Tue, 4 May 2010 05:03:39 +0800 [thread overview]
Message-ID: <t2s91b13c311005031403h37c5e066va6870a3ae0a79420@mail.gmail.com> (raw)
In-Reply-To: <4BDF2A02.1050907@drmicha.warpmail.net>
On Tue, May 4, 2010 at 3:54 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> You may mean something like
>
> git log --no-walk --format="%d [%h %an %ad %s]" --branches
>
> although Jeff will tell you to use
>
> git for-each-ref --format="%(refname:short) [%(objectname) %(authorname)
> %(authordate) %(subject)]" refs/heads
changed to refs/remotes, it works well, thanks,
git for-each-ref --format='%(refname:short)%09[%(objectname)
%(authorname) %(authordate:relative) %(subject)]' refs/remotes
> and will probably know how to abbreviate the objectname here ;)
>
> Cheers,
> Michael
>
--
Cheng Renquan (程任全), Singapore
prev parent reply other threads:[~2010-05-03 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 18:31 [RFC] git branch --status ? Cheng Renquan
2010-05-03 19:54 ` Michael J Gruber
2010-05-03 21:03 ` Cheng Renquan [this message]
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=t2s91b13c311005031403h37c5e066va6870a3ae0a79420@mail.gmail.com \
--to=crquan@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).