From: Andries Brouwer <aebr@win.tue.nl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andries Brouwer <aebr@win.tue.nl>,
"J.A. Magallon" <jamagallon@able.es>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: libata update posted
Date: Sun, 14 Sep 2003 21:38:21 +0200 [thread overview]
Message-ID: <20030914213821.A11134@pclin040.win.tue.nl> (raw)
In-Reply-To: <3F64A4BD.6030906@pobox.com>; from jgarzik@pobox.com on Sun, Sep 14, 2003 at 01:26:21PM -0400
On Sun, Sep 14, 2003 at 01:26:21PM -0400, Jeff Garzik wrote:
> > This shows why defkeymap.c is not generated in the kernel build
> > but distributed.
>
> There is a difference between distributing generated files, and checking
> generated files into a repository... I do not advocate changing the
> tarball, just the BK repo behind it.
So you would like to remove defkeymap.c from the bitkeeper repository.
Can you briefly explain why?
I am not a bk user so have no feeling for what one would like bk to do.
But it seems to me that if defkeymap.c is only a generated file when
no kbd headers have changed, while in the opposite case one needs a
private version of loadkeys until the next version of kbd has been
distributed, it is easier to regard it as part of the kernel source.
Andries
next prev parent reply other threads:[~2003-09-14 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 3:23 libata update posted Jeff Garzik
2003-09-13 20:56 ` J.A. Magallon
2003-09-13 21:28 ` Jeff Garzik
2003-09-14 9:12 ` Andries Brouwer
2003-09-14 17:26 ` Jeff Garzik
2003-09-14 19:38 ` Andries Brouwer [this message]
2003-09-14 20:09 ` Jeff Garzik
2003-09-14 21:09 ` Andries Brouwer
2003-09-14 21:36 ` Jeff Garzik
2003-09-14 21:38 ` James Bottomley
2003-09-14 22:18 ` Andries Brouwer
2003-09-16 19:34 ` Pavel Machek
2003-09-13 21:13 ` J.A. Magallon
2003-09-13 21:38 ` Jeff Garzik
2003-09-14 22:27 ` Hugo Mills
2003-09-14 22:31 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-10-05 23:15 Jeff Garzik
2003-10-05 23:41 ` Bartlomiej Zolnierkiewicz
2003-08-13 3:40 Jeff Garzik
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=20030914213821.A11134@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).