From: "Lars Hjemli" <hjemli@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Teach git-branch -v and -w options
Date: Sun, 22 Oct 2006 22:50:06 +0200 [thread overview]
Message-ID: <8c5c35580610221350q7107286eqd2ee8c5a4b09d341@mail.gmail.com> (raw)
In-Reply-To: <7vy7r83x9f.fsf@assigned-by-dhcp.cox.net>
[the gitlist fell off my first reply, so I've put it back...]
On 10/22/06, Junio C Hamano <junkio@cox.net> wrote:
> I was almost going to say that your patch saddened me because
> doing builtin-branch on top of Linus's packed-refs work (which
> means doing the series on top of "next") was part of my plan,
Heh, I don't want to compete with your c-skills :-)
> If you are aware of Kristian's patch that is a good news. I do
> not have much objection to add optional frills to git-branch
> listing output, but I'd rather not see it done in the shell
> implementation. Doing anything on the current git-branch.sh
> means that would need to be re-done later.
Agreed. I'll try and come up with a builtin instead, and let you worry
about more interesting stuff.
--
larsh
prev parent reply other threads:[~2006-10-22 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 11:30 [PATCH 0/3] Add -v and -w options to git-branch Lars Hjemli
[not found] ` <5245bfe3982f5c23841229af9f548f982b9c60c3.1161516129.git.hjemli@gmail.com>
2006-10-22 11:30 ` [PATCH 1/3] Fix usagestring for git-branch Lars Hjemli
[not found] ` <00a2e5d38382cea6ff991f60c42923092e1d4dfc.1161516129.git.hjemli@gmail.com>
2006-10-22 11:30 ` [PATCH 2/3] Refactor git-branch Lars Hjemli
[not found] ` <18d62bea290e360a4b5b44df9f23265c5e77964e.1161516129.git.hjemli@gmail.com>
2006-10-22 11:30 ` [PATCH 3/3] Teach git-branch -v and -w options Lars Hjemli
2006-10-22 19:35 ` Junio C Hamano
2006-10-22 19:55 ` Lars Hjemli
[not found] ` <8c5c35580610221254r7a5a009cg7ee9a9d5821f5e99@mail.gmail.com>
[not found] ` <7vy7r83x9f.fsf@assigned-by-dhcp.cox.net>
2006-10-22 20:50 ` Lars Hjemli [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=8c5c35580610221350q7107286eqd2ee8c5a4b09d341@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).