From: Lars Hjemli <hjemli@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] Extend git-branch list output
Date: Sun, 22 Oct 2006 00:33:21 +0200 [thread overview]
Message-ID: <1161470004894-git-send-email-hjemli@gmail.com> (raw)
This patch-series is on top of my previous patch to git-branch.sh
Shortlog:
[PATCH 1/3] Make git-branch honor -v when showing remote branches
[PATCH 2/3] git-branch: Add -w option to adjust branchname column width
[PATCH 3/3] Update documentation for git-branch
Diffstat:
Documentation/git-branch.txt | 8 ++++-
git-branch.sh | 79 +++++++++++++++++++++++++++--------------
2 files changed, 59 insertions(+), 28 deletions(-)
next reply other threads:[~2006-10-21 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 22:33 Lars Hjemli [this message]
2006-10-21 22:33 ` [PATCH 1/3] Make git-branch honor -v when showing remote branches Lars Hjemli
2006-10-21 22:33 ` [PATCH 2/3] git-branch: Add -w option to adjust branchname column width Lars Hjemli
2006-10-21 22:33 ` [PATCH 3/3] Update documentation for git-branch Lars Hjemli
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=1161470004894-git-send-email-hjemli@gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
/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).