On Mon, Mar 14, 2016 at 11:20:34AM +0000, Lester Caine wrote:
>
> The fact that git does not handle modular projects at all well was my
> main objection to being forced to use it. CVS had it's faults, but also
> it's good points, and being able to create a release made from cherry
> picked parts of the code tree was one which was blown apart by the git
> requirement that every part has it's own repository. It's only recently
> that the idea that 'sub-modules' are perhaps useful to some projects
> that is concept has started to be developed,
Recently? Git submodules were introduced in 2007.
> but essentially making each
> element of the code base a separate repo also requires that each is
> synced and track individually.
There is --recurse-submodules option to both "git fetch" and "git pull"
(and also "git push"). And, of course, "git submodule foreach".
> Anybody remember the good old days when
> one could hit 'sync' and see which blocks of code had been updated ...
> one could then simply merge a block or individually scan the files of a
> block you were also working on. Not something that is easy to do with
> the current work flows forced on us by git?
You can easily do a complete fetch and then decide which parts to pull.
Michal Kubecek
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
