Junio C Hamano writes:
> Pranit Bauva writes:
>
>>> If you know you haven't finished, you may use WIP (work in progress)
>>> instead of RFC in the title.
>>
>> I wasn't familiar with this tag. I will keep it in mind. And this is not
>> included in
Pranit Bauva writes:
>> If you know you haven't finished, you may use WIP (work in progress)
>> instead of RFC in the title.
>
> I wasn't familiar with this tag. I will keep it in mind. And this is not
> included in Documentation/SubmittingPatches , so I will send a patch
on Sep 17 00:00:00 2001
>> From: Pranit Bauva <pranit.ba...@zoho.com>
>> Date: Fri, 26 Feb 2016 07:14:18 +0530
>> Subject: [PATCH/RFC] git-commit: add a commit.verbose config variable
>From hence forth I will take that into consideration.
> Talking about this in the commi
14:18 +0530
> Subject: [PATCH/RFC] git-commit: add a commit.verbose config variable
Drop these four lines. The first is only meaningful in your
repository, and the rest are picked up automatically by git-am from
the email envelope.
> Since many people always run the command with this
On Thu, Feb 25, 2016 at 1:27 PM, Matthieu Moy
wrote:
>
>> +commit.verbose::
>> + A boolean to specify whether to always include the verbose option
>
> Boolean is usually written with a capital letter.
I disagree here, ("grep -riI boolean" suggestes to only
Pranit Bauva <pranit.ba...@zoho.com> writes:
> From c273a02fc9cab9305cedf6e37422e257a1cc3b1e Mon Sep 17 00:00:00 2001
> From: Pranit Bauva <pranit.ba...@zoho.com>
> Date: Fri, 26 Feb 2016 07:14:18 +0530
> Subject: [PATCH/RFC] git-commit: add a commit.verbose confi
>From c273a02fc9cab9305cedf6e37422e257a1cc3b1e Mon Sep 17 00:00:00 2001
From: Pranit Bauva <pranit.ba...@zoho.com>
Date: Fri, 26 Feb 2016 07:14:18 +0530
Subject: [PATCH/RFC] git-commit: add a commit.verbose config variable
Since many people always run the command with this option,
7 matches
Mail list logo