On Fri, May 31, 2013 at 10:20 PM, Ashutosh Bapat <
ash...@en...> wrote:
> Hi All,
> I am curious as why we don't want PostgreSQL tags in XC? While debugging
> some merge problems, I found that it will be helpful to have those tags in
> XC repository as well to know where and what happened in PG repository and
> relate it to the XC branching, tagging etc. So, why don't we have PG tags
> in XC? Can somebody answer it?
>
Because you don't need them, and minimizing the number of tags in the
XC-only code makes it more understandable. If you want to include the
vanilla tags, and as Postgres and XC repositories share 99% of similar
history, what developers *should* do when developing with PG or XC code is
using a single GIT repository containing 2 remote definitions to vanilla
Postgres and XC such as you can create local branches based on the 2
remotes and then they can do direct comparisons between them or a given
object/branch/tag. If you have the 2 remotes defined and fetched, the
vanilla tags will be included. Having such a development model for a fork
is a huge advantage, model getting even better thanks to git.
Having 2 remotes pointing to PG and XC is also the method to use when
merging code from one remote to the other, through local branches based on
different remotes.
--
Michael
|
