On Wed, Mar 16, 2016 at 10:11:17PM +0100, Dimitry Sibiryakov wrote:
> 16.03.2016 22:03, Michal Kubecek wrote:
> > One of the advantages of getting used to use these "topic" branches
> > rather than adding commits directly to a local copy of "upstream" branch
> > (e.g. B3_0_Release here) is that it allows you to work on several
> > different bugs or features and simply switch between the branches as
> > needed. The workflow could look like
>
> It is fine, but what will happen to gigabytes of object files in
> temp dir after switching from one branch to another? Full rebuild
> every time?
Not necessarily. Switching between two topic branches forked from e.g.
B3_0_Release should leave most of the source tree intact. However, to be
able to build within the local git repository and still use it for devel
work, we will need to create a .gitignore file covering all files and
directories generated by the build (which is a certainly a good idea).
For branches forked from very different upstream branches, you can
either use multiple clones or (with recent git versions, IIRC since 2.5
or 2.6) multiple worktrees sharing the same objects (git worktree ...).
It's a matter of scale, I would say. Working with linux kernel most of
the time, I kind of fail to see Firebird repository as big or taking too
long to build from scratch. :-)
> > With Github workflow, one usually pushes into his fork of the original
> > repository and then creates a pull request using the web interface.
>
> How many years can live a pull request without resolution on GitHub?
That depends on the project and its maintainers, of course. But this is
a problem completely orthogonal to the choice of VCS or VCS hosting
service.
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
