public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Here's a unified kernel git repo covering 0.0.1 to the present.
Date: Mon, 01 Aug 2011 23:10:21 -0500	[thread overview]
Message-ID: <4E3778AD.8020306@landley.net> (raw)
In-Reply-To: <20110802011851.GC16305@fieldses.org>

On 08/01/2011 08:18 PM, J. Bruce Fields wrote:
> On Fri, Jul 22, 2011 at 10:45:57PM -0500, Rob Landley wrote:
>> Ever done a "git annotate" that stops at 2.6.12-rc2, and wanted to see 
>> the full history?  Here's an repository that goes all the way back to
>> 0.0.1 (through bitkeeper and all those old tarballs), which otherwise
>> works as normal (git pull updates it from Linus's tree, you can commit
>> to it and branch from it, etc)
>>
>> Here's the tarball:
>>
>>   http://www.kernel.org/pub/linux/kernel/people/landley/linux-fullhist.tar.bz2
>>
>> To install it:
>>
>>   1) Download, extract, cd into the directory.
>>   2) git checkout -f
>>   3) git pull
> 
> Note if you use git-replace instead of grafts then you should be able to
> post it as a normal clone-able git tree.
> 
> --b.

*shrug*  It worked for me?  I posted a link to the script it came from,
you could ping that guy or tweak his script to do what you want.

My general response to git trees is to convert them to mercurial because
git's UI is utterly horrible, and its infrastructure overcomplicated.
That said, it's what the kernel uses, so it's ubiquitous.

I got pointed at another full history git repo earlier today, maybe
it'll work better for you?  Haven't tried it myself, I'm pretty happy
with the one I posted.

  https://twitter.com/mirell/status/98086867580354560

Rob

      reply	other threads:[~2011-08-02  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23  3:45 Here's a unified kernel git repo covering 0.0.1 to the present Rob Landley
2011-08-02  1:18 ` J. Bruce Fields
2011-08-02  4:10   ` Rob Landley [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=4E3778AD.8020306@landley.net \
    --to=rob@landley.net \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@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