On 16/01/2020 15:00, Jakub Jelinek wrote:
On Wed, Jan 15, 2020 at 10:48:23PM +, Joseph Myers wrote:
A reasonable replacement for those push rules might be command aliases
(e.g. "git upush " to push the user branch ).
Would we have then separate aliases for pushing to one vendor branch and
On Wed, Jan 15, 2020 at 10:48:23PM +, Joseph Myers wrote:
> A reasonable replacement for those push rules might be command aliases
> (e.g. "git upush " to push the user branch ).
Would we have then separate aliases for pushing to one vendor branch and
another vendor branch?
Couldn't one alias
On Wed, Jan 15, 2020 at 5:56 PM Joseph Myers
wrote:
> A reasonable replacement for those push rules might be command aliases
> (e.g. "git upush " to push the user branch ).
>
And/or git mpush for push origin HEAD:master
Jason
A reasonable replacement for those push rules might be command aliases
(e.g. "git upush " to push the user branch ).
--
Joseph S. Myers
jos...@codesourcery.com
On 14/01/2020 14:55, Richard Earnshaw (lists) wrote:
Originally, it seemed like a good idea to add automatic 'push' rules
to the git configuration, so that personal- and vendor-space commits
would automatically push to the right place. Unfortunately, this
changes git's behaviour and with these s
Originally, it seemed like a good idea to add automatic 'push' rules
to the git configuration, so that personal- and vendor-space commits
would automatically push to the right place. Unfortunately, this
changes git's behaviour and with these settings "git push" will try to
push all branches in a l