From: jaseem abid <jaseemabid@gmail.com>
To: Ryan Lortie <desrt@desrt.ca>
Cc: git@vger.kernel.org
Subject: Re: 'git branch' when origin branch with same name exists
Date: Tue, 19 Jun 2012 20:48:57 +0530 [thread overview]
Message-ID: <CAH-tXsAoRj2oE76Mrv4jGCKDbzOihPZJF+0OTEpB1Ojf7CDv8A@mail.gmail.com> (raw)
In-Reply-To: <4FE091FB.7020202@desrt.ca>
On Tue, Jun 19, 2012 at 8:21 PM, Ryan Lortie <desrt@desrt.ca> wrote:
> hi,
>
> After helping someone on IRC who got themselves into a bit of a problem, I
> have a feature request for git.
>
> In this case, the user wanted to checkout a branch of a module. They did:
>
> git clone git://git.gnome.org/gtk+
> cd gtk+
> git branch gtk-3-4
>
> Obviously this is a user error, but it's a pretty innocent one, and puts the
> user in a bad state. When they figure they should have typed "git checkout
> gtk-3-4" it is already too late -- they will be taken onto their
> locally-created copy of the master branch.
>
> So feature request: 'git branch' should not allow creating a local branch
> that has the same name as a branch that already exists on 'origin' (or any
> remote?) without some sort of --force flag. It could instead helpfully say:
>
> """
>
> The branch you are trying to create already exists on the origin.
> Are you sure you don't want to checkout this branch using
> 'git checkout gtk-3-4'
>
> """
>
> or something like that.
>
> Thoughts?
Dont know much about this but to me it looks like a good feature.
--
Jaseem Abid
http://jaseemabid.github.com
next prev parent reply other threads:[~2012-06-19 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 14:51 'git branch' when origin branch with same name exists Ryan Lortie
2012-06-19 15:18 ` jaseem abid [this message]
2012-06-19 15:35 ` Michael Schubert
2012-06-19 15:54 ` Ryan Lortie
2012-06-19 16:17 ` Philippe Vaucher
2012-06-19 15:57 ` Angus Hammond
2012-06-19 16:06 ` Konstantin Khomoutov
2012-06-19 17:06 ` Ryan Lortie
2012-06-20 8:31 ` Andreas Ericsson
2012-06-19 17:21 ` Thomas Rast
2012-06-19 18:31 ` Junio C Hamano
2012-06-19 20:44 ` Ryan Lortie
2012-06-19 21:32 ` Junio C Hamano
2012-06-19 21:50 ` Ryan Lortie
2012-06-19 23:21 ` Phil Hord
2012-06-20 17:32 ` Junio C Hamano
2012-06-20 17:51 ` Matthieu Moy
2012-06-20 18:07 ` Junio C Hamano
2012-06-19 18:22 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH-tXsAoRj2oE76Mrv4jGCKDbzOihPZJF+0OTEpB1Ojf7CDv8A@mail.gmail.com \
--to=jaseemabid@gmail.com \
--cc=desrt@desrt.ca \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).