On Wed, 4 May 2016 17:30:39 -0700 (PDT)
Moi wrote:
> "
> *These per-customer branches contain customer-specific customizations
> and receive "integration merges" from the "pristine" branch when
> needed
> -- typically when a new bug fix or a feature gets implemented there.
>
…or merge, or rebase, whatever way you can get pristine’s changes to
vendor. This all depends on your workflow. If you don’t have one, I would
go with merges.
Gergely Polonkai
[image: https://]about.me/gergely.polonkai
"
*These per-customer branches contain customer-specific customizations
and receive "integration merges" from the "pristine" branch when needed
-- typically when a new bug fix or a feature gets implemented there. *"
what does "integration merges" mean? Does it mean cherry pick those fixes
On Tue, 3 May 2016 06:25:19 -0700 (PDT)
Moi wrote:
> Can we make use of Git to implement White Label concept?
> Eg, I have a product that are sold to customer A and customer B. If
> customer B needs to customize on some screens which customer A
> doesn't need, how do I
Moi writes:
> Can we make use of Git to implement White Label concept?
> Eg, I have a product that are sold to customer A and customer B. If
> customer B needs to customize on some screens which customer A doesn't
> need, how do I implement the white label using Git?
I'm
Can we make use of Git to implement White Label concept?
Eg, I have a product that are sold to customer A and customer B. If
customer B needs to customize on some screens which customer A doesn't
need, how do I implement the white label using Git?
--
You received this message because you are