Roman Zippel wrote:
>>Well, my basic preference is
>>
>>* something other than Config.new (the original name in your config system)
>>* something other than Config.in
>>
>>I think it is a mistake to name a totally different format the same name
>>as an older format... even "config.in" would be better than "Config.in"...
>>
>>
>
>My first plan was to use Config.in, but I can't overwrite the old files
>yet, so I named it Config.new. Personally I only prefer that it starts
>with a capital letter (like Makefile, Readme), so it's at the top of a
>dir listing, but otherwise I don't care much about the name.
>
Simple and boring but how about "Config2.in" or "Config-2.in" ???
Regards,
Brendan Simon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:31 EST