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

Git Worktree Support (Git 2.5) #3590

Closed
pankajazad opened this issue Mar 15, 2017 · 12 comments
Closed

Git Worktree Support (Git 2.5) #3590

pankajazad opened this issue Mar 15, 2017 · 12 comments

Comments

@pankajazad
Copy link

A new worktree command has been introduced in Git 2.5. It allows you to maintain multiple checked out work trees of the same root repository. It's fantastic. The support for worktree in git extensions will be greatly appriciated.

@vbjay
Copy link
Contributor

vbjay commented Mar 15, 2017

#3249

@vbjay
Copy link
Contributor

vbjay commented Mar 15, 2017

@pmiossec
Copy link
Member

@pankajazad
I have updated the pull request and it should now works.
Feel free to test and give feedback...

@jbialobr jbialobr added this to the 2.50 milestone Mar 19, 2017
@pankajazad
Copy link
Author

@pmiossec
Thanks a lot.

@pankajazad
Copy link
Author

pankajazad commented Mar 23, 2017

installed the recently released 2.48.02 version but couldn't find any menu/button for git worktree. How should I use worktree feature using gitextensions. I'm using Git-2.12.0-64-bit

@jbialobr
Copy link
Member

This issue is tagged with the 2.50 milestone. That means that it will be available in the 2.50 version.

@pankajazad
Copy link
Author

That's true for #3590. But #3249, which actually implements the worktree support is already integrated in master branch and 2.49.02 tagged version actually contains the corresponding source code. Maybe it's not exposed via GUI yet.

@pmiossec
Copy link
Member

@pankajazad it seems that you have some difficulties reading the history.
Yes #3249 is merged in master (that will be the next to release 2.50)but no, that's not in 2.49.2.
What you see is just that the 2.49.2 branch has been merged into master.

PS: and that's always funny someone outside of a project that try to explain to the maintainer of a project what he did himself ;-)

@jbialobr
Copy link
Member

gitext

@pankajazad
Copy link
Author

@pmiossec, @jbialobr
Thanks for explaining. I have understood now. Apologies for the trouble caused.

@jbialobr
Copy link
Member

No problem.

@jbialobr
Copy link
Member

@pmiossec Thank you for implementing this - it is very nice feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants