Differences in Revisions: Initial Git setup

»
Newer Revision
March 23 at 6:26 pm
Added two sentences to make clear that an @ipfire.org mail address is not strictly necessary for patch submission. That the usage of a private repository is a valid option.
# Initial Git setup
 
## Introduce yourself
 
At first you have to introduce yourself to git. That means we tell it our name and mail address.
(Please use "First Name Second Name" and your @ipfire.org address)
 
```
git config --global user.name "Your Name Comes Here"
git config --global user.email you@yourdomain.example.com
```
 
Please note that you need to use a working and a non-trash email address if you submit patches. Also pick one that is long-lived so that people can contact you later.
Please note that you need to use a working and a non-trash email address if you submit patches. Also pick one that is long-lived so that people can contact you later. An @ipfire.org email address is not required for patch submission. You can of course use your own private git repository.
 
If you want colourful output you can use the following command:
 
```
git config --global color.ui auto
```
 
## Setting up Git for email
 
```
git config --global sendemail.smtpencryption ssl
git config --global sendemail.smtpserver submissions.ipfire.org
git config --global sendemail.smtpserverport 465
git config --global sendemail.smtpuser USERNAME
```
 
### Default destinations
 
If you are sending email to always the same destination, you may set this up as default to not be prompted enter the same destination over and over again. It does not make sense to do this globally, but for the main IPFire repositories this would be:
 
```
git config sendemail.to development@lists.ipfire.org
```
 
### Disable certificate verification
 
On systems running IPFire 2 the SSL certificate of the mail server cannot be verified. To disable verification run the following command:
 
```
git config --global sendemail.smtpsslcertpath ''
```