Re: [PATCH v3] clang-format: add a comment about the meaning/status of the

2017-10-02 Thread Ramsay Jones
On 02/10/17 18:21, Brandon Williams wrote: > On 10/02, Junio C Hamano wrote: >> From: Stephan Beyer >> >> Having a .clang-format file in a project can be understood in a way that >> code has to be in the style defined by the .clang-format file, i.e., you >> just have to run clang-format over all

Re: [PATCH v3] clang-format: add a comment about the meaning/status of the

2017-10-02 Thread Brandon Williams
On 10/02, Junio C Hamano wrote: > From: Stephan Beyer > > Having a .clang-format file in a project can be understood in a way that > code has to be in the style defined by the .clang-format file, i.e., you > just have to run clang-format over all code and you are set. > > This unfortunately is n

Re: [PATCH v3] clang-format: add a comment about the meaning/status of the

2017-10-02 Thread Stephan Beyer
Hi, On 10/02/2017 01:37 AM, Junio C Hamano wrote: > diff --git a/.clang-format b/.clang-format > index 56822c116b..7670eec8df 100644 > --- a/.clang-format > +++ b/.clang-format > @@ -1,4 +1,8 @@ > -# Defaults > +# This file is an example configuration for clang-format 5.0. > +# > +# Note that this

[PATCH v3] clang-format: add a comment about the meaning/status of the

2017-10-01 Thread Junio C Hamano
From: Stephan Beyer Having a .clang-format file in a project can be understood in a way that code has to be in the style defined by the .clang-format file, i.e., you just have to run clang-format over all code and you are set. This unfortunately is not yet the case in the Git project, as the for