On Mon, 2017-11-06 at 11:24 +0900, Junio C Hamano wrote:
> Kaartic Sivaraam writes:
>
> We usually use the word "gently" to when we enhance an operation
> that used to always die on failure. When there are tons of callsite
> to the original operation F(), we
Kaartic Sivaraam writes:
> This parameter allows the branchname validation functions to
> optionally return a flag specifying the reason for failure, when
> requested. This allows the caller to know why it was about to die.
> This allows more useful error messages to
On Friday 03 November 2017 12:12 AM, Stefan Beller wrote:
On Thu, Nov 2, 2017 at 1:39 AM, Kaartic Sivaraam
wrote:
On Thursday 02 November 2017 12:24 PM, Kaartic Sivaraam wrote:
Signed-off-by: Kaartic Sivaraam
Signed-off-by: Kaartic
On Thu, Nov 2, 2017 at 1:39 AM, Kaartic Sivaraam
wrote:
> On Thursday 02 November 2017 12:24 PM, Kaartic Sivaraam wrote:
>>
>> Signed-off-by: Kaartic Sivaraam
>> Signed-off-by: Kaartic Sivaraam
>
>
> I just
On Thursday 02 November 2017 12:24 PM, Kaartic Sivaraam wrote:
Signed-off-by: Kaartic Sivaraam
Signed-off-by: Kaartic Sivaraam
I just now saw this small glitch as a consequence of recently
changing my email address. I would prefer
This parameter allows the branchname validation functions to
optionally return a flag specifying the reason for failure, when
requested. This allows the caller to know why it was about to die.
This allows more useful error messages to be given to the user when
trying to rename a branch.
The flags
This parameter allows the branchname validation functions to
optionally return a flag specifying the reason for failure, when
requested. This allows the caller to know why it was about to die.
This allows more useful error messages to be given to the user when
trying to rename a branch.
The flags
7 matches
Mail list logo