(e.g. /etc/gitconfig, or $HOME/.gitconfig), they can be unset later in
the more specific repository config by the empty string.
Add tests and update documentation as well.
Signed-off-by: Marius Paliga
---
Documentation/config.txt | 29 +
Documentation/git-push.txt | 10 --
buil
> --o::
> ---push-option::
> +-o ::
> +--push-option=::
> Transmit the given string to the server, which passes them to
> the pre-receive as well as the post-receive hook. The given string
> must not contain a NUL or LF character.
> - When no `--push-option ` is given
(e.g. /etc/gitconfig, or $HOME/.gitconfig), they can be unset later in
the more specific repository config by the empty string.
Add tests and update documentation as well.
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 ++
builtin/push.c | 26 +---
t/
I just sent a patch to a new thread which is not what I wanted.
However I already sent the same patch a few days ago:
https://public-inbox.org/git/CAK7vU=2ePR3jQsgu=rxsmrxytaahqxc0sfrn5yozlzqzp2z...@mail.gmail.com/
2017-10-17 6:01 GMT+02:00 Junio C Hamano :
> Thais Diniz writes:
>
>> +Just to cl
on as well.
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 ++
builtin/push.c | 12
t/t5545-push-options.sh| 77 ++
3 files changed, 92 insertions(+)
diff --git a/Documentation/git-push.txt b/Documentation/gi
nfig
(/etc/gitconfig), they can be unset later in the more specific
repository config by setting the string to the empty string.
Add tests and documentation as well.
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 ++
builtin/push.c | 12
t/t5545-push-options.
ory config by setting the string to the empty string.
Add tests and documentation as well.
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 +++
builtin/push.c | 11 ++-
t/t5545-push-options.sh| 48 ++
3 files c
In the light of the above the "default" may be correct, but I don't
have a problem
with any name.
Marius
2017-10-11 15:38 GMT+02:00 Junio C Hamano :
> Marius Paliga writes:
>
>> @@ -505,6 +509,12 @@ static int git_push_config(const char *k, const
>> char *v,
st_has_string(&push_options, item->string)) {
New (fixed) patch follows...
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 +++
builtin/push.c | 11 ++-
t/t5545-push-options.sh| 48 ++
3 files cha
Including proposed patch...
Signed-off-by: Marius Paliga
---
Documentation/git-push.txt | 3 +++
builtin/push.c | 11 ++-
t/t5545-push-options.sh| 48 ++
3 files changed, 61 insertions(+), 1 deletion(-)
diff --git a
Hi Stefan,
I will look at it.
Thanks,
Marius
2017-10-03 18:53 GMT+02:00 Stefan Beller :
> On Tue, Oct 3, 2017 at 3:15 AM, Marius Paliga wrote:
>> There is a need to pass predefined push-option during "git push"
>> without need to specify it explicitly.
>>
>&g
There is a need to pass predefined push-option during "git push"
without need to specify it explicitly.
In another words we need to have a new "git config" variable to
specify string that will be automatically passed as "--push-option"
when pushing to remote.
Something like the following:
git co
12 matches
Mail list logo
