2013/2/19 Ramkumar Ramachandra:
>
> What is your usecase? If you have a local branch with the same name
> as on the remote, why wouldn't you want to push-to-update it when you
> make changes in the branch? In other words, why doesn't push.default
> = matching suffice for most practical purposes.
Blind wrote:
> 2013/2/19 Ramkumar Ramachandra:
>> No. I don't see why push.default is limiting.
>
> I just want to find a way to exclude a branch (or infact a group of
> branches) from $git push --all.
> so when I read your thing, I thought for a second that it could be a
> possibility... But seem
2013/2/19 Ramkumar Ramachandra:
> No. I don't see why push.default is limiting.
I just want to find a way to exclude a branch (or infact a group of
branches) from $git push --all.
so when I read your thing, I thought for a second that it could be a
possibility... But seems its not the case.
...
Blind wrote:
> If I understand correctly,
> in your scenario the branches with branch..pushremote
> will be still included in the $git push --all?
Yes, this is correct.
> Are you considering some way to exclude a branch from "push --all"
> (branch..push = always, explicit, never... for example)?
If I understand correctly,
in your scenario the branches with branch..pushremote
will be still included in the $git push --all?
Are you considering some way to exclude a branch from "push --all"
(branch..push = always, explicit, never... for example)?
Or maybe, if the branch is already marked as s
Junio C Hamano wrote:
> struct bp { const char *branch; const char *remotename; };
>
> static int pushremote(const char *var, const char *val, void *cb)
> {
> struct bp *bp = cb;
> const char *name, *key;
> int namelen;
>
>
Ramkumar Ramachandra writes:
> Junio C Hamano wrote:
>
>> In other words, does it make sense to read branch.$name.pushremote
>> for all the other irrelevant branches?
>>
>> In yet other words, perhaps adding pushremote_name to the branch
>> structure is unneeded, and you only need this single glo
Junio C Hamano wrote:
> Ramkumar Ramachandra writes:
>
>> diff --git a/remote.c b/remote.c
>> index e53a6eb..d6fcfc0 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;
>> +
Ramkumar Ramachandra writes:
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 9b11597..0b3b1f8 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -727,6 +727,12 @@ branch..remote::
> remote to fetch from/push to. It defaults to `origin`
Ramkumar Ramachandra writes:
> Comments are welcome.
As the first cut, I would have expected the series to start from
more general (not "only this branch"), with later follow-up to let
more specific configuration.
Also I'd prefer to see the "push" semantics (e.g. "what does
upstream mean in th
This new configuration variable overrides the remote in
`branch..remote` for pushes. It is useful in the typical
scenario, where the remote I'm pulling from is not the remote I'm
pushing to. Although `remote..pushurl` is similar, it does not
serve the purpose as the URL would lack corresponding r
11 matches
Mail list logo
