Dave Borowitz dborow...@google.com writes:
---
Does the lack of sign-off indicate something (like this is just a
'what do people think?' weatherbaloon not yet a serious submission)?
+push.gpgSign::
+ May be set to a boolean value, or the string 'if-possible'. A
+ true value causes
On Mon, Aug 17, 2015 at 1:13 PM, Junio C Hamano gits...@pobox.com wrote:
Dave Borowitz dborow...@google.com writes:
---
Does the lack of sign-off indicate something (like this is just a
'what do people think?' weatherbaloon not yet a serious submission)?
+push.gpgSign::
+ May be set
Dave Borowitz dborow...@google.com writes:
The issue is that if both _ALWAYS and _IF_POSSIBLE are set,
git_transport_push interprets it as _ALWAYS. But, we are also supposed
to prefer explicit command-line options to config values.
Suppose we parsed config first, then options. If the user
Junio C Hamano gits...@pobox.com writes:
Dave Borowitz dborow...@google.com writes:
The issue is that if both _ALWAYS and _IF_POSSIBLE are set,
git_transport_push interprets it as _ALWAYS. But, we are also supposed
to prefer explicit command-line options to config values.
Suppose we parsed
On Mon, Aug 17, 2015 at 3:42 PM, Junio C Hamano gits...@pobox.com wrote:
Dave Borowitz dborow...@google.com writes:
The issue is that if both _ALWAYS and _IF_POSSIBLE are set,
git_transport_push interprets it as _ALWAYS. But, we are also supposed
to prefer explicit command-line options to
5 matches
Mail list logo
