From: Junio C Hamano <gitster@pobox.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] [RED] git-init: Cannot setup bare repository
Date: Mon, 27 Aug 2007 03:01:53 -0700 [thread overview]
Message-ID: <7vtzqljnxq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070827095523.GQ1219@pasky.or.cz> (Petr Baudis's message of "Mon, 27 Aug 2007 11:55:23 +0200")
Petr Baudis <pasky@suse.cz> writes:
> On Mon, Aug 27, 2007 at 10:51:04AM CEST, Johannes Schindelin wrote:
>> On Sun, 26 Aug 2007, Petr Baudis wrote:
>> ...
>> You were too busy playing Go, probably, so you missed my patch which tried
>> to fix this issue. Alas, it broke more than it fixed, so it was just
>> worked around for git-clone --bare.
>
> AFAICS that patch is already applied as well; I tried to ask on IRC
> for more fixes but seemed there is none and Junio almost threatened to
> even release 1.5.3 with this bug. ;-) Well, I just needed something that
> would fix this on repo.or.cz which totally broke after upgrade to new
> Git version.
Heh, "threaten" is a good word. Could you two help me with this
issue? I suspect you (and probably Shawn) have the most "old
fashioned" scripts that rather rely on pre-work-tree behaviour
and have better chance than others to catch unintended side
effects like the current "git --bare init" issues.
prev parent reply other threads:[~2007-08-27 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 20:45 [PATCH] [RED] git-init: Cannot setup bare repository Petr Baudis
2007-08-27 8:51 ` Johannes Schindelin
2007-08-27 9:55 ` Petr Baudis
2007-08-27 10:01 ` Junio C Hamano [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=7vtzqljnxq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).