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

Add git-fetch aliases to git plugin #3749

Closed
wants to merge 16 commits into from
Closed

Add git-fetch aliases to git plugin #3749

wants to merge 16 commits into from

Conversation

pcurry
Copy link

@pcurry pcurry commented Apr 5, 2015

Adds two aliases for git fetch activities to keep updated with remote repositories.

irnnr and others added 16 commits June 2, 2014 13:39
Vagrant 1.6 introduces a couple new commands, including the `version` command.
The `version` command shows the currently installed version information and
also checks for new updates available.
Vagrant 1.5 introduced Vagrant Share to allow remote access to a Vagrant
environment. This adds support for the `share` and `connect` commands.
Vagrant 1.5 added Vagrant Cloud to share boxes. Some boxes
may be protected, the `login` command allows to access those
protected boxes from Vagrant Cloud.
Vagrant 1.6 introduced the `global-status` command which allows
to get a quick overview of all active Vagrant environments for the
currently logged in user.
Vagrant 1.6 introduced the `global-status` command which allows
to get a quick overview of all active Vagrant environments for the
currently logged in user.
…-my-aliases

Merging my upstream with this branch
Merge in the branch so I stop getting errors
ncanceill added a commit to ncanceill/oh-my-zsh that referenced this pull request Apr 5, 2015
@ncanceill ncanceill mentioned this pull request Apr 5, 2015
5 tasks
@ncanceill
Copy link
Contributor

This is now fixed in #2790.

Please do not merge this PR, since it has become polluted by empty merge commits.

@pcurry
Copy link
Author

pcurry commented Apr 5, 2015

Verified @ncanceill 's branch had the aliases I use. This PR doesn't need to go forward.

@pcurry pcurry closed this Apr 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants