From: Greg KH <greg@kroah.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, tglx@kernel.org
Subject: Re: older git archive access broken in 1.2.0?
Date: Mon, 13 Feb 2006 22:15:29 -0800 [thread overview]
Message-ID: <20060214061529.GA853@kroah.com> (raw)
In-Reply-To: <7vek26wkwu.fsf@assigned-by-dhcp.cox.net>
On Mon, Feb 13, 2006 at 09:48:17PM -0800, Junio C Hamano wrote:
> Greg KH <greg@kroah.com> writes:
>
> > I was trying to find where something changed in the historical Linux
> > kernel git tree:
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/
> >
> > when I noticed that the latest version of git doesn't seem to like this
> > archive. I can't clone it, but 'git log' and 'git whatchanged' seems to
> > work fine.
>
> I think 1.2.0 may be a coincidence. history.git/ mistakenly has
> an extra .git subdirectory underneath it. Removing it should
> make things to work again I suspect.
Ah, doh, that was simple. Thanks for the quick response.
greg k-h
next prev parent reply other threads:[~2006-02-14 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 5:06 older git archive access broken in 1.2.0? Greg KH
2006-02-14 5:48 ` Junio C Hamano
2006-02-14 6:15 ` Greg KH [this message]
2006-02-14 7:00 ` Thomas Gleixner
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=20060214061529.GA853@kroah.com \
--to=greg@kroah.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tglx@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).