From: Junio C Hamano <junkio@cox•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Do not verify filenames in a bare repository
Date: Fri, 19 Jan 2007 16:56:03 -0800 [thread overview]
Message-ID: <7vmz4ebjoc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0701200149010.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Sat, 20 Jan 2007 01:52:16 +0100 (CET)")
This feels very sane. Thanks.
A handful tests to make sure it catches the cases wants to catch
and it does not hiccup with the cases it shouldn't catch would
be appropriate, though.
next prev parent reply other threads:[~2007-01-20 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 12:02 BUG: git --bare log HEAD Han-Wen Nienhuys
2007-01-20 0:52 ` [PATCH] Do not verify filenames in a bare repository Johannes Schindelin
2007-01-20 0:56 ` Junio C Hamano [this message]
2007-01-20 1:05 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-01-20 2:09 Johannes Schindelin
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=7vmz4ebjoc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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