On Tuesday 08 May 2018 08:49 AM, Junio C Hamano wrote:
> Junio C Hamano <gitster@xxxxxxxxx> writes:
>
>> I couldn't quite get what you meant by "(but not the other way
>> around)". Did you mean
>>
>> $ git push --force ../child2 refs/tags/*:refs/tags/*
>>
>> should not become non-forcing version because of the (lack of)
>> prefix on the refspec does not trump the --force command line
>> option?
When I was reading the commit message, I had the same doubt about what
"(but not the other way around)" actually meant but I assumed it meant
that "the `--no-force` in the command line does not override the '+' in
the refspec". Maybe the commit message could be updated to clarify this?
--
Sivaraam
QUOTE:
“The most valuable person on any team is the person who makes everyone
else on the team more valuable, not the person who knows the most.”
- Joel Spolsky
Sivaraam?
You possibly might have noticed that my signature recently changed from
'Kaartic' to 'Sivaraam' both of which are parts of my name. I find the
new signature to be better for several reasons one of which is that the
former signature has a lot of ambiguities in the place I live as it is a
common name (NOTE: it's not a common spelling, just a common name). So,
I switched signatures before it's too late.
That said, I won't mind you calling me 'Kaartic' if you like it [of
course ;-)]. You can always call me using either of the names.
KIND NOTE TO THE NATIVE ENGLISH SPEAKER:
As I'm not a native English speaker myself, there might be mistaeks in
my usage of English. I apologise for any mistakes that I make.
It would be "helpful" if you take the time to point out the mistakes.
It would be "super helpful" if you could provide suggestions about how
to correct those mistakes.
Thanks in advance!
Attachment:
signature.asc
Description: OpenPGP digital signature
