- Git guide for Linux wireless users and developers
- Cloning latest wireless-testing
- Get the latest updates
- Review the changes last registered
- To review changes made to wireless drivers
- To review changes made to mac80211
- Hacking on Linux wireless
- Check available branches
- Reviewing changes between commmits
- Merging git branches
- Checkout code as it was from specific commit
- Delete branches
- No need to download more kernel tarballs
- Generate patches
- Sending patches
Git guide for Linux wireless users and developers
This is a quick git-guide for Linux users and developers with emphasis on Linux wireless. The latest Linux wireless development takes place on John Linville's wireless-testing git tree.
Cloning latest wireless-testing
First, clone the wireless-testing.git tree
git-clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git cd wireless-testing
Get the latest updates
You will want to update your local git repository to match what John has last committed. You can do this as follows.
Review the changes last registered
To review changes made to wireless drivers
git-log -p drivers/net/wireless/
To review changes made to mac80211
git-log -p net/mac80211/
You get the idea.
Hacking on Linux wireless
If you'd like to hack on Linux wireless you can create own branch based on the one you are using. This is so you don't screw your current branch up.
git-checkout -b my-fix-for-foo # hack hack hack # To get a diff of your work: git-diff > my_changes.diff # Or if you just want to read them: git-diff # To revert to the original state of the branch: git-checkout -f # If instead you want to commit git-commit -a
Check available branches
Suppose you have created a few branches, and just are not sure what you have anymore.
# To view local branches git-branch -l # To view all remote branches git-branch -r
Reviewing changes between commmits
Suppose you want to get the log and diff between two commits.
# get the SHA of two commits git-log # Then get the diff of them, by showing the logs in between git-log -p d8a285c8f83f728be2d056e6d4b0909972789d51..9202ec15da36ca060722c363575e0e390d85fb71 # Since SHAs are pretty unique you can just give it a short version # and it will try to match what is right: git-log -p d8a28..9202e
Merging git branches
Say you have two local branches, and I want to merge them. If you're on local branch my-latest and I want to merge with local branch my-fix-for-foo, you would do:
git-pull . my-fix-for-foo
Checkout code as it was from specific commit
Suppose you want to checkout what the codebase looked like at a specific commit SHA. You can do this with branches.
# Long form: git-checkout -b view-commit-foo d8a285c8f83f728be2d056e6d4b0909972789d51 # Or short form: git-checkout -b view-commit-foo d8a28
If you are fed up with a branch delete it. You must not be on that branch so go into another one.
git-checkout master git-branch -D old-branch
No need to download more kernel tarballs
You can simply make your current directory look like a specific tag blessed by Linus (or Linville).
git-checkout -b v2.6.27-rc7 v2.6.27-rc7
Say you have 3 commits and you want to send the patches now.
git format-patch -o some-dir d8a285c8f83f728be2d056e6d4b0909972789d51..9202ec15da36ca060722c363575e0e390d85fb71 # this is equivalent to, this is the short form git format-patch -n -o some-dir d8a28..9202e
Where d8a28 was the last commit before you started hacking and 9202e is the current head, meaning the commit ID of your latest commit.
Read git-send-email man page. But here is a quick summary for those who just want to get it to work. Keep in mind git-send-email is a perl script and is usually shipped separately from git core.
You can install your favorite mailer, one option is to use ssmtp.
Setting up ssmtp
Below is an example config that works with an exchange server, in etc/ssmtp/ssmtp.conf:
email@example.com mailhub=smtp.company.com hostname=smtp.company.com FromLineOverride=YES UseSTARTTLS=YES AuthUser=lrodriguez AuthPass=my-uber-secret-password
Here is an example /etc/ssmtp/revaliases
user can be the username (whoami) on the system.
Once you have your mailer setup and patches in a directory, review them so they are correct. Once all done send them out using: