From: Jeff King <peff@peff.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org
Subject: Re: [PATCH v2] Bisect reset: remove bisect refs that may have been packed.
Date: Thu, 15 Nov 2007 03:52:59 -0500 [thread overview]
Message-ID: <20071115085259.GA30913@sigill.intra.peff.net> (raw)
In-Reply-To: <20071115084934.GN14735@spearce.org>
On Thu, Nov 15, 2007 at 03:49:34AM -0500, Shawn O. Pearce wrote:
> What's this obsession with whitespace in refnames? Twice in like
> two days people are talking about whitespace in refnames.
I even had Junio convinced at one point!
I am not actually creating such refs, but I think my brain was still
fried from the URL encoding discussion, and I was overly paranoid about
spaces.
-Peff
next prev parent reply other threads:[~2007-11-15 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 7:18 [PATCH v2] Bisect reset: remove bisect refs that may have been packed Christian Couder
2007-11-15 8:18 ` Junio C Hamano
2007-11-15 8:27 ` Johannes Sixt
2007-11-15 8:49 ` Shawn O. Pearce
2007-11-15 8:52 ` Jeff King [this message]
2007-11-15 12:10 ` Johannes Schindelin
2007-11-15 8:34 ` Junio C Hamano
2007-11-15 9:00 ` [PATCH 1/3] git-bisect: war on "sed" Junio C Hamano
2007-11-15 9:29 ` Miles Bader
2007-11-15 9:36 ` Wincent Colaiuta
2007-11-15 9:53 ` Miles Bader
2007-11-15 10:06 ` Andreas Ericsson
2007-11-15 10:14 ` David Kastrup
[not found] ` <86tznn4y7v.fsf@lola.quinscape.zz>
2007-11-15 11:00 ` Miles Bader
2007-11-15 11:18 ` David Kastrup
2007-11-15 12:59 ` Miles Bader
2007-11-15 9:01 ` [PATCH 2/3] git-bisect: use update-ref to mark good/bad commits Junio C Hamano
2007-11-15 9:01 ` [PATCH 3/3] git-bisect: modernize branch shuffling hack 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=20071115085259.GA30913@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=spearce@spearce.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).