forked from rapid7/metasploit-framework
-
Notifications
You must be signed in to change notification settings - Fork 0
Git Gotchas
jlee-r7 edited this page Jun 20, 2012
·
1 revision
If you've created a topic branch on your personal fork as described in Metasploit Development Environment, rebasing from upstream/master is a little tricky. This link explains what can go wrong: http://blog.evan.pro/a-simple-explanation-of-git-rebase
Basically, rebasing will put you into a state where you have a local commit with a different sha1 from your remote commit of the same patch. So don't do that. Instead, use git merge upstream/master
if you need to pull in new commits from rapid7's fork. But! As @tpope explains, it may not be worth the clogged up history, so don't do that either. http://tbaggery.com/2008/04/18/example-git-workflows-maintaining-a-long-lived-topic-branch.html
- Home Welcome to Metasploit!
- Using Metasploit A collection of useful links for penetration testers.
-
Setting Up a Metasploit Development Environment From
apt-get install
togit push
. - Landing Pull Requests Working with other people's contributions.
- Using Git All about Git and GitHub.
- Acceptance Guidelines What should your modules look like?
- Contributing to Metasploit Be a part of our open source community.