From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
GIT Mailing-list <git@vger.kernel.org>,
"Hart, Darren" <darren.hart@intel.com>,
"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Subject: Re: Alternates corruption issue
Date: Tue, 31 Jan 2012 16:59:09 -0600 [thread overview]
Message-ID: <20120131225909.GA13780@burratino> (raw)
In-Reply-To: <20120131224240.GA3844@sigill.intra.peff.net>
Jeff King wrote:
> On Tue, Jan 31, 2012 at 04:22:58PM -0600, Jonathan Nieder wrote:
>> I admit part of the reason I care is that just putting "" first would
>> probably taken care of the more important part of
>> <http://bugs.debian.org/399041>.
>
> Would that fix it? If I understand it, the repo in question is bare with
> a ".git" directory inside it.
The layout was foo/.git/.git. The real repository was made with plain
"git init" or "git clone", and then "git svn init" or similar was run
from within .git, creating a .git subdirectory. (Something more must
have happened, actually, since the tree was weirdly sparse:
$ find .git/.git
.git/.git
.git/.git/svn
.git/.git/svn/git-svn
.git/.git/svn/git-svn/.rev_db
)
In the current scheme, to access such a broken repository remotely,
you have to use a URL ".../foo". URLs pointing to foo/.git (like gitk
once used) end up rewritten as .git/.git. Of course, your patch with
the is_git_directory() will fix this specific case. :)
Not a huge deal, especially since "git svn init" prints out where it
is writing these days.
next prev parent reply other threads:[~2012-01-31 22:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 14:05 Alternates corruption issue Richard Purdie
2012-01-31 19:39 ` Jeff King
2012-01-31 20:25 ` Junio C Hamano
2012-01-31 20:44 ` Jeff King
2012-01-31 21:40 ` Jonathan Nieder
2012-01-31 21:47 ` Jeff King
2012-01-31 21:55 ` Jonathan Nieder
2012-01-31 22:05 ` Jeff King
2012-01-31 22:22 ` Jonathan Nieder
2012-01-31 22:42 ` Jeff King
2012-01-31 22:59 ` Jonathan Nieder [this message]
2012-02-02 21:59 ` Jeff King
2012-02-03 0:47 ` Junio C Hamano
2012-02-03 12:02 ` Jeff King
2012-02-03 17:38 ` Junio C Hamano
2012-02-03 21:29 ` Jeff King
2012-02-03 21:51 ` Junio C Hamano
2012-02-03 21:53 ` Jeff King
2012-02-03 14:40 ` Richard Purdie
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=20120131225909.GA13780@burratino \
--to=jrnieder@gmail.com \
--cc=Bruce.Ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=richard.purdie@linuxfoundation.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).