James C. McPherson writes:
> Stephen Lau wrote:
> > Bill Sommerfeld wrote:
> >> Perhaps more problematic: a number of kernel modules embed keywords like
> >> %I% in literal strings which become admin-visible, especially in
> >> "modstat" output.
> >> What do you propose to do about this?
> > I beli
Stephen Lau wrote:
Bill Sommerfeld wrote:
Perhaps more problematic: a number of kernel modules embed keywords like
%I% in literal strings which become admin-visible, especially in
"modstat" output.
What do you propose to do about this?
I believe the plan is to remove these...
Whoa there, tige
Bill Sommerfeld wrote:
Perhaps more problematic: a number of kernel modules embed keywords like
%I% in literal strings which become admin-visible, especially in
"modstat" output.
What do you propose to do about this?
I believe the plan is to remove these...
cheers,
steve
--
stephen lau // [EM
Bill Sommerfeld wrote:
Perhaps more problematic: a number of kernel modules embed keywords like
%I% in literal strings which become admin-visible, especially in
"modstat" output.
Hopefully it won't result in more instances like this in modinfo:
69 f5bb5000 4d91b8 187 1 nvidia (nvid
On Mon, 2006-05-22 at 17:40, Stephen Lau wrote:
> I prefer the $Id$ syntax, since it's also supported under Subversion.
Existing practice among the *BSD's is to define *specific* $Keyword$
(such as $NetBSD$/$OpenBSD$/$FreeBSD$) recognized only by the master
repository so that folks checking copie
Stephen Lau wrote:
Currently, I've got a Mercurial python hook that will expand $Id$ to
something like:
$Id: fubar 9f7070beca6e 2006-05-23 stevel $
so my proposal is to adopt a #ident syntax of:
# ident $Id$ SMI.
What do people think of this? It's easy enough to change the format,
I'd just
I just wanted to start a discussion on what format we want to use for
keywords in ON. Currently, the #ident we use is something akin to:
# ident "%Z%%M% %I% %E% SMI"
which expands out to something like:
# ident "@(#)Makefile.master1.204 06/04/13 SMI"
Currently, I've got a Mercurial
