Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 84712581c19982d32ad4fad403b378e53863c3ba Author: Sven Eckelmann sven@narfation.org Date: Fri Aug 20 09:08:59 2010 +0000
doc: batman-adv/LinuxNextTracking
84712581c19982d32ad4fad403b378e53863c3ba batman-adv/LinuxNextTracking.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/batman-adv/LinuxNextTracking.textile b/batman-adv/LinuxNextTracking.textile index c920651f..5da84712 100644 --- a/batman-adv/LinuxNextTracking.textile +++ b/batman-adv/LinuxNextTracking.textile @@ -4,7 +4,7 @@ We have currently our own branch to create patches for linux. These patches are
Other people will also create patches which may affect our code and thus we have to import them too in our codebase. In a perfect world these people will CC: us, but we aren't in a perfect world and we must ensure by our self that we get informed about them. The first approach was to check linux-next before we try to rebase our patches on top of linux-next. This created a large gap until we noticed them or we forgot them at all.
-The new approach is to create a mirror of linux-next on our server, install a small script which parses the commits in post-receive and send mails when there are changes in fails inside drivers/staging/batman-adv. This script is stolen from http://git.open-mesh.org/batman-adv/. +The new approach is to create a mirror of linux-next on our server, install a small script which parses the commits in post-receive and send mails when there are changes in fails inside drivers/staging/batman-adv. This script is stolen from http://git.open-mesh.org/batman-adv.git.
== Initial setup ==