Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

`magit-create-branch': simplify #841

Merged
merged 1 commit into from Aug 30, 2013
Merged

Conversation

praet
Copy link
Contributor

@praet praet commented Aug 30, 2013

I added the `magit-create-branch-behaviour' option back in 2011
(commit 3cf5764), but made the horrible mistake of leaving the
original behavior ("create branch at HEAD") the default.
See e.g. this thread [1] from February 2013 on the ML.

Instead of making 'at-point the default, let's just get rid of
the option altogether and always try to find a rev at point first.

Note that I'm intentionally not using magit-default-rev', as that usesmagit-guess-branch', which is very likely to offer
the previous value of HEAD instead of the current one.

[1] mid:"87k3q9pm73.fsf@debian.org"

Signed-off-by: Pieter Praet pieter@praet.org

I added the `magit-create-branch-behaviour' option back in 2011
(commit 3cf5764), but made the horrible mistake of leaving the
original behavior ("create branch at HEAD") the default.
See e.g. this thread [1] from February 2013 on the ML.

Instead of making 'at-point the default, let's just get rid of
the option altogether and always try to find a rev at point first.

Note that I'm intentionally *not* using `magit-default-rev', as
that uses `magit-guess-branch', which is very likely to offer
the *previous* value of HEAD instead of the current one.

[1] mid:"87k3q9pm73.fsf@debian.org"

Signed-off-by: Pieter Praet <pieter@praet.org>
tarsius added a commit that referenced this pull request Aug 30, 2013
@tarsius tarsius merged commit b308be6 into magit:master Aug 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants