From: Rob Landley <rob@landley.net>
To: sean <seanlkml@sympatico.ca>
Cc: torvalds@osdl.org, git@vger.kernel.org
Subject: Re: Who do I report bugs in the git source web browser thing to?
Date: Thu, 23 Mar 2006 22:06:35 -0500 [thread overview]
Message-ID: <200603232206.35242.rob@landley.net> (raw)
In-Reply-To: <BAYC1-PASMTP04E797AD25632CF422EA86AEDE0@CEZ.ICE>
On Thursday 23 March 2006 6:23 pm, sean wrote:
> On Thu, 23 Mar 2006 17:47:31 -0500
>
> Rob Landley <rob@landley.net> wrote:
> > On Thursday 23 March 2006 12:03 pm, Linus Torvalds wrote:
> > > On Thu, 23 Mar 2006, Rob Landley wrote:
> > > Pick another file, like the Makefile, to see what real history looks
> > > like (or, better yet, go into a different directory that actually sees
> > > more real work, like kernel/, and look at the history of files there).
> >
> > I was trying to find out when symlink support went in to gen_init_cpio.c,
> > so that was the only file that interested me. I forgot that the
> > bitkeeper history never got moved over.
>
> Rob,
>
> You might be able to find what you need in the bk history imported into
> git as "Linux kernel history" by Thomas Gleixner on kernel.org:
>
> http://kernel.org/git/?p=linux/kernel/git/tglx/history.git;a=history;h=e7e1
>73af42dbf37b1d946f9ee00219cb3b2bea6a;f=usr/gen_init_cpio.c
>
> Sean
Ooh, exactly what I was looking for. Thanks. (I already downloaded tarballs
to check, but I've got the bookmark for future reference.)
Rob
--
Never bet against the cheap plastic solution.
prev parent reply other threads:[~2006-03-24 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 16:43 Who do I report bugs in the git source web browser thing to? Rob Landley
2006-03-23 16:51 ` Josh Boyer
2006-03-23 17:03 ` Linus Torvalds
2006-03-23 22:47 ` Rob Landley
2006-03-23 23:23 ` sean
2006-03-23 23:23 ` sean
2006-03-24 3:06 ` 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=200603232206.35242.rob@landley.net \
--to=rob@landley.net \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.