From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Fix build error by removal of obsoleted au1x00_uart driver.
Date: Thu, 9 Feb 2006 20:53:38 +0000 [thread overview]
Message-ID: <20060209205338.GA3508@linux-mips.org> (raw)
In-Reply-To: <cda58cb80602090954s46ba0d78s@mail.gmail.com>
On Thu, Feb 09, 2006 at 06:54:05PM +0100, Franck Bui-Huu wrote:
> 2006/2/9, Ralf Baechle <ralf@linux-mips.org>:
> > When cloning such a repository git isn't actually downloading the
> > .git/info/grafts file. This results in such errors. I don't know of a
> > way to get git to do this right. You may download the file manually
>
> you can't. It seems that graft thing is, for now, only used to change
> your _own_ repository's history. Fetching from a "cautorized"
> repository is a risky job and you might have bad results.
It works for me (TM).
> It's going to change with the "shallow-clone" thing, but I don't know
> when it will come out...
There are many problems with "cautorized" repositories, some with the
current implementation, some more fundamental ones. Such as what is
the cut-off criterium? The MIPS git repository also contains the objects
of Linus's tree [1]. So a tag like linux-2.6.15 as the line for truncation
isn't working too well because I'll only truncate the Linux/MIPS history
but that'll still leave all of Linus's tree - well over 130,000 objects -
in the tree.
Anyway, I'm trying to maintain a homebrew shallow variant of the tree
for the time being until git provides a better instrument for the job.
Ralf
[1] Not Linus's tags to avoid confusion. They could easily be pulled from
Linus tree into a separate branch. Similar for Marcelo's 2.4 tree.
prev parent reply other threads:[~2006-02-10 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 15:43 [PATCH] Fix build error by removal of obsoleted au1x00_uart driver Atsushi Nemoto
2006-02-09 15:49 ` Ralf Baechle
2006-02-09 16:25 ` Atsushi Nemoto
2006-02-09 16:44 ` Ralf Baechle
2006-02-09 17:54 ` Franck Bui-Huu
2006-02-09 20:53 ` Ralf Baechle [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=20060209205338.GA3508@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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