On Sat, 3 Sep 2016 08:13:13 +0200
Bruno Raoult <[email protected]> wrote:
> I am new here, so feel free to tell me if I am wrong.
Welcome!
> I am participating to Eulyptula challenge, and of course had a look on
> Documentation/CodingStyle.
>
> As I use GNU/Emacs (yes, I know, Evil Tool, according to Linus :-), I
> took the lines in Chapter 9, which are supposed to switch to kernel
> style if the source is in a given path.
>
> I would like to do the following change, so that it works (both file
> path and linux path would be expanded the same way):
>
> diff -up linux/Documentation/CodingStyle{.orig,}
> -----------------------------------------
> --- linux/Documentation/CodingStyle.orig 2016-09-03 08:05:37.000000000
> +0200
> +++ linux/Documentation/CodingStyle 2016-09-03 08:09:00.000000000 +0200
> @@ -524,7 +524,7 @@ values. To do the latter, you can stick
>
> (add-hook 'c-mode-hook
> (lambda ()
> - (let ((filename (buffer-file-name)))
> + (let ((filename (expand-file-name (buffer-file-name))))
> ;; Enable kernel mode for the appropriate files
> (when (and filename
> (string-match (expand-file-name "~/src/linux-trees")
> -----------------------------------------
Seems like a reasonable change. Package it up as a proper patch as
described in SubmittingPatches and I'll apply it.
> I have a question, however: Which git tree should I use for such
> change ? Is there one relative to general documentation ?
As listed in the MAINTAINERS file:
T: git git://git.lwn.net/linux.git docs-next
The CodingStyle document is not particularly dynamic, though; create a
patch against any recent kernel tree and it will apply just fine.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
