Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 01 Aug 2002 20:54:58 +0900 (JST)
From:      Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
To:        phk@critter.freebsd.dk
Cc:        imp@bsdimp.com, obrien@FreeBSD.org, grog@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/conf files src/sys/contrib/dev/acpica acconfig.h acenv.h acfreebsd.h acpiosxf.h acpixf.h acutils.h dbcmds.c dbdisasm.c dbfileio.c dbxface.c psparse.c rscreate.c tbget.c utglobal.c src/sys/dev/acpica acpi.c ... 
Message-ID:  <20020801.205458.41625650.iwasaki@jp.FreeBSD.org>
In-Reply-To: <3079.1028150265@critter.freebsd.dk>
References:  <20020731.135639.119005865.imp@bsdimp.com> <3079.1028150265@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

> In message <20020731.135639.119005865.imp@bsdimp.com>, "M. Warner Losh" writes:
> 
> >Actually, just include an EDITED version of changes.  The number of
> >changes tends to be long, and a summary of them would be better.
> >
> >Of course, given that this is vendor code, and we're not quite working
> >yet, I don't think that people will CARE if they don't know exactly
> >what changed and why.  Look at some of the gcc import messages which
> >basically said "Upgrade to version N".
> 
> Well, considering that ACPI can be quite a stumbling block for laptop
> owners, I just wanted to minimal amount of text in the commit-msg
> which would indicate to me if I needed to re-test on my laptop or
> if this was likely to be a no-op for it.

Then, is importing CHANGES.txt good enough for your requirement?
If so, I'm glad to ask Intel people and do so from the next vendor
import.  I believe that it's the best solution for many people.

I'm not person from Intel, also not a ACPI CA developer actually, so
information I can get is very limited other than CHANGES.txt.
My private time is limited (especially now) as well as other
committers, however I believe I did my best within my time and am
going to make efforts as possible.
If you require to me more things, then maybe I'm not suitable person
for importing ACPI CA unfortunately :)  I can pass this work to other
committer if necessary.
But, I want to continue this actually and to follow traditional way of
vendor import into FreeBSD CVS repo.  May I?

Thanks

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020801.205458.41625650.iwasaki>