« Return to Thread: Git braindump: 2 of N: developer interaction (merge co-ordinators)
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
by Michał Górny-5
::
Rate this Message:
On Mon, 4 Jun 2012 15:57:53 -0700
Brian Harring <ferringb@...> wrote:
> Btw, good catch on package.mask. Hhadn't thought of that, that
> *will* be the most contentious point. That can be dealt w/ via
> having git on portage-1 profile format so we'd have package.mask as
> directories (which Ciaran will validly hate, and I won't like
> due to having to write the portage-1 -> PMS translater for
> rsync distribution), or coming up w/ a different way to split the
> commits across multiple files, rather than a single.
That doesn't like a 'lesser evil' to me. I'd rather see those few
conflicts and fix them once in a while rather than having to lookup
multiple package.mask files with entries split in a semi-random manner.
--
Best regards,
Michał Górny
Brian Harring <ferringb@...> wrote:
> Btw, good catch on package.mask. Hhadn't thought of that, that
> *will* be the most contentious point. That can be dealt w/ via
> having git on portage-1 profile format so we'd have package.mask as
> directories (which Ciaran will validly hate, and I won't like
> due to having to write the portage-1 -> PMS translater for
> rsync distribution), or coming up w/ a different way to split the
> commits across multiple files, rather than a single.
That doesn't like a 'lesser evil' to me. I'd rather see those few
conflicts and fix them once in a while rather than having to lookup
multiple package.mask files with entries split in a semi-random manner.
--
Best regards,
Michał Górny
signature.asc (325 bytes) « Return to Thread: Git braindump: 2 of N: developer interaction (merge co-ordinators)
| Free embeddable forum powered by Nabble | Forum Help |
