From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: BK to GIT migration status for ia64
Date: Mon, 02 May 2005 12:59:14 +0000 [thread overview]
Message-ID: <29944.1115038754@ocs3.ocs.com.au> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F035ECFEA@scsmsx401.amr.corp.intel.com>
On Mon, 2 May 2005 04:47:09 -0700,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Sun, 01 May 2005 14:19:28 +1000, Keith Owens <kaos@sgi.com> said:
>
> Keith> On Thu, 28 Apr 2005 12:19:49 -0700, "Luck, Tony"
> Keith> <tony.luck@intel.com> wrote:
> >> 1)
> >> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git
> >> 2)
> >> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/test-2.6.git
>
> Keith> Neither tree contains a refs or heads directory. Other git
> Keith> trees like linux and davem have these directories. cogito
> Keith> cg-clone and cg-update expect to find refs and heads.
>
>I cloned the test-2.6 tree last Friday (with cogito) without any
>problems. I do see the "refs" and "heads" directories. Not that it
>helps explain your problem, but just an additional data-point.
Those directories are created locally by the clone process, but they do
not exist in the kernel.org trees. I'm not sure if they are needed or
not, almost every other git tree on kernel.org has them.
next prev parent reply other threads:[~2005-05-02 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 19:19 BK to GIT migration status for ia64 Luck, Tony
2005-04-29 9:41 ` David Mosberger
2005-05-01 4:19 ` Keith Owens
2005-05-02 11:47 ` David Mosberger
2005-05-02 12:59 ` Keith Owens [this message]
2005-05-02 17:09 ` Luck, Tony
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=29944.1115038754@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-ia64@vger.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