From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: duplicated include files
Date: Sun, 4 Nov 2007 11:51:08 -0800 [thread overview]
Message-ID: <20071104115108.ea8729a2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <e5bfff550711041143i7be3cff7kd4903ed43cb4e232@mail.gmail.com>
On Sun, 4 Nov 2007 20:43:01 +0100 Marco Costalba wrote:
> On 11/4/07, Marco Costalba <mcostalba@gmail.com> wrote:
> > make includecheck does not work for me. Linux tree is from latest git.
> >
> > bash-3.2$ pwd
> > /git/linux-2.6
> >
> > bash-3.2$ make includecheck
> > find * \( -name SCCS -o -name BitKeeper -o -name .svn -o -name CVS -o
>
> BTW what's that 'BitKeeper' fossil here?
It allows people to continue using any of {CVS, SVN, BitKeeper}
for their kernel tree. The BK kernel tree is still being updated
AFAIK. (It was last time I looked, about 3 weeks ago.)
---
~Randy
next prev parent reply other threads:[~2007-11-04 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 19:41 duplicated include files Marco Costalba
2007-11-04 19:43 ` Marco Costalba
2007-11-04 19:49 ` Robert P. J. Day
2007-11-04 23:20 ` Jeremy Fitzhardinge
2007-11-05 3:49 ` Robert P. J. Day
2007-11-04 23:43 ` Bernd Petrovitsch
2007-11-04 19:51 ` Randy Dunlap [this message]
2007-11-05 10:51 ` Geert Uytterhoeven
2007-11-05 11:38 ` Marco Costalba
2007-11-14 20:40 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2007-11-04 17:31 Robert P. J. Day
2007-11-04 18:07 ` Randy Dunlap
2007-11-04 18:37 ` Robert P. J. Day
2007-11-04 18:46 ` Randy Dunlap
2007-11-04 19:03 ` Adrian Bunk
2007-11-04 19:10 ` Robert P. J. Day
2007-11-05 3:02 ` Paul Mundt
2007-11-05 8:27 ` Geert Uytterhoeven
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=20071104115108.ea8729a2.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcostalba@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