Difference between revisions of "Talk:Bering-uClibc 4.x - Developer Guide - Hints and Tips for using Git SCM"
Davidmbrooke (Talk | contribs) (Added note about leaf-git-commits) |
Davidmbrooke (Talk | contribs) (Added note about RSS) |
||
| Line 10: | Line 10: | ||
Should we consider having more than one Git "repository", one for buildtool and another for sources?<br>[[User:Davidmbrooke|Davidmbrooke]] 12:18, 5 February 2011 (UTC) | Should we consider having more than one Git "repository", one for buildtool and another for sources?<br>[[User:Davidmbrooke|Davidmbrooke]] 12:18, 5 February 2011 (UTC) | ||
| − | Do we need a '''leaf-git-commits''' mailing list to replace '''leaf-cvs-commits'''? Do we need to configure something to generate emails when changes are made? Is that what [http://sourceforge.net/apps/trac/sourceforge/wiki/Git#Commitemailhooksetup this section of the SourceForge Git page] is all about?<br>[[User:Davidmbrooke|Davidmbrooke]] 13:16, 5 February 2011 (UTC) | + | Do we need a '''leaf-git-commits''' mailing list to replace '''leaf-cvs-commits'''? Do we need to configure something to generate emails when changes are made? Is that what [http://sourceforge.net/apps/trac/sourceforge/wiki/Git#Commitemailhooksetup this section of the SourceForge Git page] is all about?<br> |
| + | Or should developers use RSS via GitWeb to get the same result?<br>[[User:Davidmbrooke|Davidmbrooke]] 13:16, 5 February 2011 (UTC) | ||
Revision as of 13:33, 5 February 2011
Right now we have the a Git repository called "leaf" with the following structure:
leaf/
bering-uclibc4/
buildtool/
files...
source/
files...
It does not seem possible to git-clone just part of a repository, so all of the source files get downloaded when initializing the build environment. Then they all get downloaded again into buildtool/sources/, and get built from there.
That doesn't seem very efficient.
Should we consider having more than one Git "repository", one for buildtool and another for sources?
Davidmbrooke 12:18, 5 February 2011 (UTC)
Do we need a leaf-git-commits mailing list to replace leaf-cvs-commits? Do we need to configure something to generate emails when changes are made? Is that what this section of the SourceForge Git page is all about?
Or should developers use RSS via GitWeb to get the same result?
Davidmbrooke 13:16, 5 February 2011 (UTC)
