On Mon, Aug 14, 2017 at 08:03:19PM -0700, Junio C Hamano wrote:
> > I'm tempted to say that "config --list" should normalize this case into:
> >
> > mysection.mykey=true
> >
> > Normally we avoid coercing values without knowing the context in which
> > they'll be used. But the syntax in the
Jeff King writes:
> On Mon, Aug 14, 2017 at 04:15:40PM -0700, Stefan Beller wrote:
>
>> + llvm-...@lists.llvm.org
>>
>> The Git community is currently discussing adopting a coding style
>> defined by clang-format, here is a bug report:
>
> Since we've added a cc, let me try to
On Mon, Aug 14, 2017 at 04:15:40PM -0700, Stefan Beller wrote:
> + llvm-...@lists.llvm.org
>
> The Git community is currently discussing adopting a coding style
> defined by clang-format, here is a bug report:
Since we've added a cc, let me try to give a little more context.
> > One more
+ llvm-...@lists.llvm.org
The Git community is currently discussing adopting a coding style
defined by clang-format, here is a bug report:
On Mon, Aug 14, 2017 at 4:06 PM, Jeff King wrote:
>
> One more oddity I found while playing with this that Git folks might run
> into:
>
>
On Mon, Aug 14, 2017 at 02:30:44PM -0700, Brandon Williams wrote:
> Changes in v2:
> * Changed a couple rules to be more inline with our coding style.
> * Added a Makefile build rule to run git-clang-format on the diff of the
>working tree to suggest style changes.
>
> I found that the
On 08/14, Brandon Williams wrote:
> Changes in v2:
> * Changed a couple rules to be more inline with our coding style.
> * Added a Makefile build rule to run git-clang-format on the diff of the
>working tree to suggest style changes.
>
> I found that the llvm project also has the
Changes in v2:
* Changed a couple rules to be more inline with our coding style.
* Added a Makefile build rule to run git-clang-format on the diff of the
working tree to suggest style changes.
I found that the llvm project also has the git-clang-format tool which will
allow for doing
7 matches
Mail list logo