From: Junio C Hamano <junkio@twinsun.com>
To: git@vger.kernel.org
Subject: Re: Is reserving the branch name "bisect" a good thing?
Date: Fri, 2 Dec 2005 23:44:07 +0000 (UTC) [thread overview]
Message-ID: <loom.20051203T004324-557@post.gmane.org> (raw)
In-Reply-To: 20051202232555.13082.qmail@science.horizon.com
<linux <at> horizon.com> writes:
> Would it be better if "git bisect" followed that rule as well?
> Otherwise, we really should document the reserved word.
I wonder if you broke "git bisect visualize" with that patch.
next prev parent reply other threads:[~2005-12-02 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 23:25 Is reserving the branch name "bisect" a good thing? linux
2005-12-02 23:44 ` Junio C Hamano [this message]
2005-12-03 13:41 ` linux
2005-12-03 19:15 ` Junio C Hamano
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=loom.20051203T004324-557@post.gmane.org \
--to=junkio@twinsun.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).