>> 	we do have them for purely kame-origin files like sys/netinet6/*.c.
>> 	this time, it was netbsd-originated, and modified-by-kame, file
>> 	(like sys/netinet/in.h).
>If the file is netbsd-originated, it is probably not shared among other BSDs,
>and KAME can easily merge the changes made by NetBSD, I guess.
>Am I missing?

	you are right that netbsd-origin file situation is much better than
	files under sys/netinet6 (for example).  since *BSD imposes different
	rules, if we tabify/untabify files shared across *BSD we get a major
	issue.  in general, tabify/untabify surely makes it harder to
	synchronize.  i could backport netbsd tabify/untabify into kame side
	when possible, but i only have limited lifetime...

	btw, #define\t is not on /usr/share/misc/style.  is there really a
	wide consensus on this?  i find it rather disturbing to have a tab
	there (if we have deep #if, we sometimes want indentation on these,
	and #define\t does not play nice if indented) .

itojun