Alex Riesen <raa.lkml@gmail.com> writes:Not necessarily. The policy is completely up to the superproject (which is git.git). Currently, the policy is "make all" and "make install" in git.git builds and installs what are considered core parts of the system which includes git-gui and gitk. gitk nor git-gui should not become useless without being in git.git (iow, their build procedure better not depend on things outside their subtree), but I do not think that is a hard requirement either. Shawn *chose* to keep git-gui buildable and installable separately as well as as part of git.git. Again I think that policy is up to individual subprojects. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Srivatsa Vaddagiri | containers (was Re: -mm merge plans for 2.6.23) |
| Benjamin Herrenschmidt | Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Patrick McHardy | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 6/7] [CCID-2/3]: Fix sparse warnings |
