BOMPARD CORENTIN p1603631 writes:
> Add the --set-upstream option to git pull/fetch
Add _a_?
> which lets the user set the upstream configuration
> (branch..merge and
> branch..remote) for the current branch.
>
> For example a typical use-case like
I don't understand this sentence. Perhaps
A
Matthieu Moy writes:
> -u::
> --set-upstream::
> For every branch that is up to date or successfully pushed, add
> upstream (tracking) reference, used by argument-less
> linkgit:git-pull[1] and other commands. For more information,
> see `branch..merge` in linkgit:git-conf
Junio C Hamano writes:
> Matthieu Moy writes:
>
>> -u::
>> --set-upstream::
>> For every branch that is up to date or successfully pushed, add
>> upstream (tracking) reference, used by argument-less
>> linkgit:git-pull[1] and other commands. For more information,
>> see `bran
Add the --set-upstream option to git pull/fetch
which lets the user set the upstream configuration
(branch..merge and
branch..remote) for the current branch.
For example a typical use-case like
git clone http://example.com/my-public-fork
git remote add main http://example.com/project-mai
>Corentin BOMPARD writes:
>
>> Add the --set-upstream option to git pull/fetch
>> which lets the user set the upstream configuration
>> for the current branch.
>
> I think it is a good idea to mention what you exactly mean by "the
> upstream configuration" here.
>
> Do you mean the "branch..merg
BOMPARD CORENTIN p1603631 writes:
> + warning(_("No source branch found. \n You need to
> specify excatly "
> + "one branch with the
> set-upstream option."));
s/excatly/exactly/
Also, this " \n " is weird, the trailing whitespac
Junio C Hamano writes:
>> --- a/Documentation/fetch-options.txt
>> +++ b/Documentation/fetch-options.txt
>> @@ -165,6 +165,11 @@ ifndef::git-pull[]
>> Disable recursive fetching of submodules (this has the same effect as
>> using the `--recurse-submodules=no` option).
>>
>> +--set-ups
Corentin BOMPARD writes:
> Add the --set-upstream option to git pull/fetch
> which lets the user set the upstream configuration
> for the current branch.
I think it is a good idea to mention what you exactly mean by "the
upstream configuration" here.
Do you mean the "branch..merge" configurat
Add the --set-upstream option to git pull/fetch
which lets the user set the upstream configuration
for the current branch.
For example a typical use-case like
git clone http://example.com/my-public-fork
git remote add main http://example.com/project-main-repo
git pull main master --set
> BOMPARD CORENTIN p1603631 writes:
>
>> Adding the --set-upstream option to git pull/fetch
>
> We usually write commit messages with imperative tone, hence "add", not
> "adding".
Fixed.
>> +/*
>> + * We want to set the current branch config following the
>> +
BOMPARD CORENTIN p1603631 writes:
> Adding the --set-upstream option to git pull/fetch
We usually write commit messages with imperative tone, hence "add", not
"adding".
> + /*
> + * We want to set the current branch config following the
> + * ref_map entry
Adding the --set-upstream option to git pull/fetch
which lets the user set the upstream configuration
for the current branch.
For example a typical use-case like
git clone http://example.com/my-public-fork
git remote add main http://example.com/project-main-repo
git pull main master --
12 matches
Mail list logo
