en:developers:documentation:git-guide
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
en:developers:documentation:git-guide [2015/01/26 09:49] 127.0.0.1 external edit |
en:developers:documentation:git-guide [2017/06/09 12:04] Kalle Valo Add git send-email settings and simplify the example |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Git guide for Linux wireless users and developers ===== | ===== 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. | + | This is a quick git-guide for Linux users and developers with emphasis on Linux wireless. The latest Linux wireless development happens in two trees: mac80211-next maintained by Johannes Berg, and wireless-drivers-next maintained by Kalle Valo. Both trees are regularly pulled into wireless-testing for integration testing; wireless-testing may therefore also be used as a base for development along with the upstream trees. |
| ===== Cloning latest wireless-testing ===== | ===== Cloning latest wireless-testing ===== | ||
| Line 12: | Line 11: | ||
| - | <code>git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git | + | <code>git clone git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git |
| cd wireless-testing</code> | cd wireless-testing</code> | ||
| Line 197: | Line 196: | ||
| 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. | 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. | + | You can install your favorite mailer, you can directly contact to your SMTP server or alternivately to use ssmtp. |
| + | |||
| + | To set your name and email in git: | ||
| + | |||
| + | <code> | ||
| + | git config --global user.name "Ed Example" | ||
| + | git config --global user.email "ed@example.com"</code> | ||
| + | |||
| + | ==== Using SMTP server directly ==== | ||
| + | |||
| + | Set SMTP settings to git: | ||
| + | <code> | ||
| + | git config --global sendemail.smtpencryption tls | ||
| + | git config --global sendemail.smtpserver mail.example.com | ||
| + | git config --global sendemail.smtpuser ed@example.com | ||
| + | git config --global sendemail.smtpserverport 587 | ||
| + | git config --global sendemail.smtppass myverysecretpassword</code> | ||
| - | ==== Setting up ssmtp ==== | + | ==== Setting up ssmtp (optional) ==== |
| Below is an example config that works with an exchange server, in etc/ssmtp/ssmtp.conf: | Below is an example config that works with an exchange server, in etc/ssmtp/ssmtp.conf: | ||
| Line 225: | Line 240: | ||
| Once you have your mailer setup and patches in a directory, review them so they are correct. Once all done send them out using: | Once you have your mailer setup and patches in a directory, review them so they are correct. Once all done send them out using: | ||
| + | <code> | ||
| + | git send-email --to linux-wireless@vger.kernel.org --cc maintainer-of-driver@example.com some-dir/</code> | ||
| - | <code># Note new versions of git use: git send-email | + | Where some-dir is where you stashed your patches. Keep in mind that if you are submitting a series it helps to send an introductory PATCH [0/n] as well, where n is the number of patches you want to send. You can add this to the git-send-email queue easily using ''--cover-letter'' when generating patches using git-format-patch. Be sure to edit the patch 0000-foo then. git-send-email will pick it up when you specify the directory :) |
| - | git send-email --no-chain-reply-to --from "Random Developer <hacker@company.com>" --to linville@tuxdriver.com --cc linux-wireless@vger.kernel.org --cc maintainer-of-driver@some-cool.org some-dir/</code> | + | |
| - | Where some-dir is where you stashed your patches. Keep in mind that if you are submitting a series it helps to send an introductory PATCH [0/n] as well, where n is the number of patches you want to send. You can add this to the git-send-email queue easily using --cover-letter when generating patches using git-format-patch. Be sure to edit the patch 0000-foo then. git-send-email will pick it up when you specify the directory :) | + | |
en/developers/documentation/git-guide.txt · Last modified: 2024/02/07 19:11 by Alexis Lothoré
Page Tools
