On Wed, 28 Sep 2005, Paul Jackson wrote: > > Too bad that first line doesn't start "Author:" instead of "From:". > Oh well - I see Andrew already suggested that, and you declined. > (You should'a listened to him ;). The "From:" rule has been implicit in my tools for a _loong_ time, and switching to "Author:" would just break the tools for no actual technical gain. Not just the tools, either, since Andrew isn't the only one who follows that From: rule - it would break "people". So you'd have to make the tools accept _both_ "From:" and "Author:", and I personally prefer an _unambiguously_ slightly misnamed thing over some "either X or Y" where X is slightly misnamed but accepted because it's the one more commonly used. It's like the unix "creat()" system call. Sure, it would make more sense to add the "e", but it wouldn't actually really _help_ anybody. As to documenting the "From:" thing - yes, we probably should. It's quite commonly used. Linus - 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/
- References:
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- From: Paul Jackson <pj@sgi.com>
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- From: Hirokazu Takahashi <taka@valinux.co.jp>
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- From: Paul Jackson <pj@sgi.com>
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- From: Hirokazu Takahashi <taka@valinux.co.jp>
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- From: Paul Jackson <pj@sgi.com>
- [PATCH 1/3] CPUMETER: add cpumeter framework to the CPUSETS
- From: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
- Re: [PATCH 1/3] CPUMETER: add cpumeter framework to the CPUSETS
- From: Paul Jackson <pj@sgi.com>
- Re: [PATCH 1/3] CPUMETER: add cpumeter framework to the CPUSETS
- From: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
- [PATCH][BUG] fix memory leak on reading cpuset files after seeking beyond eof
- From: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
- [PATCH] cpuset read past eof memory leak fix
- From: Paul Jackson <pj@sgi.com>
- Re: [PATCH] cpuset read past eof memory leak fix
- From: Linus Torvalds <torvalds@osdl.org>
- Re: [PATCH] cpuset read past eof memory leak fix
- From: Paul Jackson <pj@sgi.com>
- Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- Prev by Date: Re: [PATCH] cpuset read past eof memory leak fix
- Next by Date: RE: [RFC PATCH] New SA_NOPRNOTIF sigaction flag
- Previous by thread: Re: [ckrm-tech] Re: [PATCH] cpuset read past eof memory leak fix
- Next by thread: Re: [PATCH 1/3] CPUMETER: add cpumeter framework to the CPUSETS
- Index(es):
