All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schubert <mschub@elegosoft.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: More support on branch description?
Date: Thu, 19 Jan 2012 16:14:45 +0100	[thread overview]
Message-ID: <4F183365.5010607@elegosoft.com> (raw)
In-Reply-To: <CACsJy8D0_EB6jN7KxpzLtnPnj0HjdU6sNHJRyqXJf-2-ZNatFA@mail.gmail.com>

On 01/19/2012 03:14 PM, Nguyen Thai Ngoc Duy wrote:
> The coming v1.7.9 will introduce branch description, mainly used in
> integration process. I think we could make it useful for users who
> don't extensively use request-pull/format-patch. Showing a short
> summary along with branch name in "git branch" would be nice. "branch
> -v" is already used for something else, maybe we can come up with
> another option, or "-v -v"? Another place we could show branch
> description is "git status". What do you think?

Junio suggested a new option "--verbose-format" for branch some weeks
ago:

	http://thread.gmane.org/gmane.comp.version-control.git/186727

I planned on working on it, but haven't found the time yet nor do I
really know which way to go.? (pretty.c seems to be the right
place for format code, but it's very commit format specific atm.)

  reply	other threads:[~2012-01-19 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 14:14 More support on branch description? Nguyen Thai Ngoc Duy
2012-01-19 15:14 ` Michael Schubert [this message]
2012-01-19 15:24   ` Nguyen Thai Ngoc Duy
2012-01-19 22:22 ` Junio C Hamano
2012-01-20  8:24   ` Nguyen Thai Ngoc Duy

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=4F183365.5010607@elegosoft.com \
    --to=mschub@elegosoft.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.