From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [RFC/PATCH] Introduce remote.pushdefault
Date: Sat, 9 Feb 2013 13:20:31 +0530 [thread overview]
Message-ID: <CALkWK0nq9Nir9NA9CxyajazrTxNURA_6r4kN6c3v+G8MtQtqsg@mail.gmail.com> (raw)
In-Reply-To: <7v4nhm1s85.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Ramkumar Ramachandra <artagnon@gmail.com> writes:
>
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index 9b11597..82a4a78 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -1884,6 +1884,10 @@ receive.updateserverinfo::
>> If set to true, git-receive-pack will run git-update-server-info
>> after receiving data from git-push and updating refs.
>>
>> +remote.pushdefault::
>> + The remote to push to by default. Overrides the
>> + branch-specific configuration `branch.<name>.remote`.
>
> It feels unexpected to see "I may have said while on this branch I
> push there and on that branch I push somewhere else, but no, with
> this single configuration I'm invalidating all these previous
> statements, and all pushes go to this new place".
>
> Shouldn't the default be the default that is to be overridden by
> other configuration that is more specific? That is, "I would
> normally push to this remote and unless I say otherwise that is all
> I have to say, but for this particular branch, I push to somehwere
> else".
Oops, I meant to have it overriden by branch-specific configuration. Fixed now.
>> diff --git a/builtin/push.c b/builtin/push.c
>> index 42b129d..d447a80 100644
>> --- a/builtin/push.c
>> +++ b/builtin/push.c
>> @@ -322,7 +322,7 @@ static int push_with_options(struct transport *transport, int flags)
>> static int do_push(const char *repo, int flags)
>> {
>> int i, errs;
>> - struct remote *remote = remote_get(repo);
>> + struct remote *remote = pushremote_get(repo);
>> const char **url;
>> int url_nr;
>>
>> diff --git a/remote.c b/remote.c
>> index e53a6eb..08bb803 100644
>> --- a/remote.c
>> +++ b/remote.c
>> @@ -48,6 +48,7 @@ static int branches_nr;
>>
>> static struct branch *current_branch;
>> static const char *default_remote_name;
>> +static const char *pushremote_name;
>> static int explicit_default_remote_name;
>>
>> static struct rewrites rewrites;
>> @@ -349,6 +350,14 @@ static int handle_config(const char *key, const char *value, void *cb)
>> const char *subkey;
>> struct remote *remote;
>> struct branch *branch;
>> + if (!prefixcmp(key, "remote.")) {
>> + name = key + 7;
>> + if (!strcmp(name, "pushdefault")) {
>> + if (!value)
>> + return config_error_nonbool(key);
>> + pushremote_name = xstrdup(value);
>> + }
>> + }
>> if (!prefixcmp(key, "branch.")) {
>> name = key + 7;
>> subkey = strrchr(name, '.');
>> @@ -388,8 +397,6 @@ static int handle_config(const char *key, const char *value, void *cb)
>> add_instead_of(rewrite, xstrdup(value));
>> }
>> }
>> - if (prefixcmp(key, "remote."))
>> - return 0;
>
> Why is this no longer needed?
>
> All the remainder of this function is about "remote.*" config and
> this rejects other keys, like "user.name", etc.
I'm sorry. I read that as if (!prefixcmp(key, "remote.")), which is
an entirely different thing. Fixed now.
Thanks.
next prev parent reply other threads:[~2013-02-09 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 7:19 [RFC/PATCH] Introduce branch.<name>.pushremote Ramkumar Ramachandra
2013-02-08 8:21 ` Junio C Hamano
2013-02-08 9:02 ` [RFC/PATCH] Introduce remote.pushdefault Ramkumar Ramachandra
2013-02-08 20:11 ` Junio C Hamano
2013-02-09 7:50 ` Ramkumar Ramachandra [this message]
2013-03-17 0:30 ` Ramkumar Ramachandra
2013-03-17 5:48 ` Jeff King
2013-03-18 9:02 ` Ramkumar Ramachandra
2013-03-17 6:10 ` Junio C Hamano
2013-02-08 20:04 ` [RFC/PATCH] Introduce branch.<name>.pushremote Junio C Hamano
2013-02-09 7:46 ` Ramkumar Ramachandra
2013-02-09 20:00 ` Junio C Hamano
2013-02-10 15:41 ` Ramkumar Ramachandra
2013-02-11 6:16 ` Blind
2013-02-19 9:27 ` Ramkumar Ramachandra
2013-02-19 11:18 ` Blind
2013-02-19 11:30 ` Ramkumar Ramachandra
2013-02-19 11:51 ` Blind
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkWK0nq9Nir9NA9CxyajazrTxNURA_6r4kN6c3v+G8MtQtqsg@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).