From: Kalle Valo <Kalle.Valo@iki.fi>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Change git-branch to list branches
Date: Wed, 17 Aug 2005 23:15:18 +0300 [thread overview]
Message-ID: <871x4s7221.fsf@litku.valo.iki.fi> (raw)
In-Reply-To: <87br3w73at.fsf@litku.valo.iki.fi> (Kalle Valo's message of "Wed, 17 Aug 2005 22:48:26 +0300")
Kalle Valo <Kalle.Valo@iki.fi> writes:
> Junio C Hamano <junkio@cox.net> writes:
>
>> I do not think we have agreed to limit ourselves to a flat
>> namespace under refs/heads without subdirectories. Something
>> like what git-show-branches-script does when $# == 0, perhaps?
>
> I didn't realise this. I'll send a revised patch soon.
Ah, but you fixed it already. Thanks!
--
Kalle Valo
next prev parent reply other threads:[~2005-08-17 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 20:44 [PATCH] Add git-branches-script Amos Waterland
2005-08-16 17:53 ` Kalle Valo
2005-08-16 17:58 ` [PATCH] Change git-branch to list branches Kalle Valo
2005-08-16 21:08 ` Junio C Hamano
2005-08-17 19:48 ` Kalle Valo
2005-08-17 20:15 ` Kalle Valo [this message]
2005-08-17 20:37 ` [PATCH] Add git-branches-script Miguel Bazdresch
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=871x4s7221.fsf@litku.valo.iki.fi \
--to=kalle.valo@iki.fi \
--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).