New Revision: https://blackfin.uclinux.org/doku.php?id=processes
Old Revision: https://blackfin.uclinux.org/doku.php?id=processes&rev=1
435747339
Edit Summary: fix graph
@@ -281,12 +281,12 @@
The Linux kernel is a integral part of this, but is handled in a more st
ructured manner, due to it's development process.
<graphviz dot>
digraph {
- "blackfin.uclinux.org git" -> "blackfin git tree" -> "Linus git tree" -
> "official Linux release"
- "blackfin.uclinux.org git" -> "driver maintainer git tree" -> "Linus gi
t tree" -> "official Linux release"
+ "blackfin.uclinux.org svn" -> "blackfin git tree" -> "Linus git tree" -
> "official Linux release"
+ "blackfin.uclinux.org svn" -> "driver maintainer git tree" -> "Linus gi
t tree" -> "official Linux release"
"Linus git tree" -> "blackfin git tree"
- "official Linux release" -> "blackfin.uclinux.org git"
+ "official Linux release" -> "blackfin.uclinux.org svn"
}
</graphviz>
For example;
@@ -300,10 +300,10 @@
U-Boot is managed in a similar way, where we send patches to the mainlin
e maintainers, and periodically update the local git to become synced with
the mainline project.
<graphviz dot>
digraph {
- "blackfin.uclinux.org git" -> "release"
- "mainline U-Boot" -> "blackfin.uclinux.org git" -> "mainline U-Boot" ;
+ "blackfin.uclinux.org svn" -> "release"
+ "mainline U-Boot" -> "blackfin.uclinux.org svn" -> "mainline U-Boot" ;
}
</graphviz>
and the Blackfin/GNU Toolchain, which is managed in a similar way, excep
t for the bits and pieces (like the eclipse plugins, and ldr utils, which
we create, and maintain 100%):
|