Re: Feature Request: enhance Git-GUI's Checkout Branch screen

David, Option C - when you say "[in git-cola] when the remote branch is selected it strips of the remote part and automatically fills in the name field with that", are you referring to the Branch Create screen or the Branch Checkout screen? Your description matches the Create screen. And for

Re: Feature Request: enhance Git-GUI's Checkout Branch screen

Junio, I can appreciate the amount of clutter you'd get with the ancient behavior. That said, I'd be willing to live with it. I personally prefer to see all the branches coming and going - if the branches are good enough for upstream, they're good enough for me (I'm really good an ignoring

Re: Feature Request: enhance Git-GUI's Checkout Branch screen

John Medema writes: > Option D has the downside that it changes the behavior of more code > (cmdline and gui), which is why I didn't suggest it before. It also > has the downside of making the branch list longer. But that's the > nature of cloning; if I copy a full

Feature Request: enhance Git-GUI's Checkout Branch screen

Git gurus, throw this one on your to-do list: This is a feature request to enhance the Git GUI to make it easier to checkout non-existing branches that exist upstream. Apologies if this is not the correct place for feature requests. Scenario: Upstream repo has 4 branches - master, develop,

Re: Feature Request: enhance Git-GUI's Checkout Branch screen

On Thu, Sep 03, 2015 at 10:08:24AM -0700, John Medema wrote: > Git gurus, throw this one on your to-do list: > > This is a feature request to enhance the Git GUI to make it easier to > checkout non-existing branches that exist upstream. Apologies if this > is not the correct place for feature