User Tools

Site Tools


en:users:drivers:ath10k:sources

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:users:drivers:ath10k:sources [2017/06/14 07:58]
Kalle Valo Move the -rc release example to submittingpatches page and remove duplicate information
en:users:drivers:ath10k:sources [2018/05/29 13:29] (current)
Kalle Valo [Git branches] Use master branch also for testing
Line 22: Line 22:
 ath.git contains multiple branches: ​ ath.git contains multiple branches: ​
  
-  * **master:** The default branch selected when cloning the tree. Everyone working on any ath drivers (ath10k, ath9k, ath6kl etc) should use this branch as the baseline for patches. Follows Bob Copeland'​s wireless-testing tree and contains the latest -rc release from Linus Torvalds + latest wireless + latest ath patches ​ from ath-next and ath-current branches. The branch is rebased every time it's updated. Due to unclean history bisect will not work, better to use ath-next (or ath-current) for bisecting. ​+  * **master:** The default branch selected when cloning the tree. Everyone working on any ath drivers (ath10k, ath9k, ath6kl etc) should use this branch as the baseline for patches ​and when testing latest code. Follows Bob Copeland'​s wireless-testing tree and contains the latest -rc release from Linus Torvalds + latest wireless + latest ath patches from ath-next and ath-current branches. The branch is rebased every time it's updated. Due to unclean history bisect will not work, better to use ath-next (or ath-current) for bisecting. ​
   * **ath-next:​** Based on Kalle'​s wireless-drivers-next tree and will be periodically merged to wireless-drivers-next and scheduled for the next release under works (not for the current -rc releases). ath patches are commited to this branch first and then merged to the master branch. For bisect runs it's better to use this branch instead of the master branch. All patches adding new features or low priority fixes go to this branch.   * **ath-next:​** Based on Kalle'​s wireless-drivers-next tree and will be periodically merged to wireless-drivers-next and scheduled for the next release under works (not for the current -rc releases). ath patches are commited to this branch first and then merged to the master branch. For bisect runs it's better to use this branch instead of the master branch. All patches adding new features or low priority fixes go to this branch.
   * **ath-current:​** Based on Kalle'​s wireless-drivers tree and will be periodically merged to wireless-drivers and scheduled for the current release under works (for the upcoming -rc release). Only critical fixes.   * **ath-current:​** Based on Kalle'​s wireless-drivers tree and will be periodically merged to wireless-drivers and scheduled for the current release under works (for the upcoming -rc release). Only critical fixes.
en/users/drivers/ath10k/sources.txt ยท Last modified: 2018/05/29 13:29 by Kalle Valo