Todd Zullinger writes:
> Seeing that the error output when using it tells the user to "use
> '--track' or '--set-upstream-to' instead," should we perhaps also
> remove the --set-upstream entry entirely? That's reads:
>
>--set-upstream::
>As this option had
Junio C Hamano wrote:
Todd Zullinger writes:
Support for the --set-upstream option was removed in 52668846ea
(builtin/branch: stop supporting the "--set-upstream" option,
2017-08-17), after a long deprecation period.
Remove the option from the command synopsis for consistency.
Todd Zullinger writes:
> Support for the --set-upstream option was removed in 52668846ea
> (builtin/branch: stop supporting the "--set-upstream" option,
> 2017-08-17), after a long deprecation period.
>
> Remove the option from the command synopsis for consistency. Replace
>
Martin Ågren wrote:
On 16 November 2017 at 08:46, Todd Zullinger wrote:
I noticed that --set-upstream was still in the synopsis for git branch. I
don't think it was left there intentionally. I looked through the thread where
support for the option was removed and didn't
On Thursday 16 November 2017 04:19 PM, Martin Ågren wrote:
On 16 November 2017 at 08:46, Todd Zullinger wrote:
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index d6587c5e96..159ca388f1 100644
--- a/Documentation/git-branch.txt
+++
On 16 November 2017 at 08:46, Todd Zullinger wrote:
> Support for the --set-upstream option was removed in 52668846ea
> (builtin/branch: stop supporting the "--set-upstream" option,
> 2017-08-17), after a long deprecation period.
>
> Remove the option from the command synopsis for
Support for the --set-upstream option was removed in 52668846ea
(builtin/branch: stop supporting the "--set-upstream" option,
2017-08-17), after a long deprecation period.
Remove the option from the command synopsis for consistency. Replace
another reference to it in the description of
7 matches
Mail list logo