From: "Matthieu Moy"
"Philip Oakley" writes:
From: "Matthieu Moy"
But then the maintainer is not the one picking changes from it (you're
sending them by email), so the "maintainer" label is not really accurate
in the diagram:
+ ---
+| UPSTREAM | maintain
"Philip Oakley" writes:
> From: "Matthieu Moy"
>
>> But then the maintainer is not the one picking changes from it (you're
>> sending them by email), so the "maintainer" label is not really accurate
>> in the diagram:
>>
>> + ---
>> +| UPSTREAM | maintainer |
From: "Matthieu Moy"
"Philip Oakley" writes:
From: "Matthieu Moy"
I don't think you will find a name that fits all use-cases. IHMO, best
is to pick one rather general use-case, make the explanations for it,
and maybe explain somewhere that there are variants.
If the fork is completely pri
"Philip Oakley" writes:
> From: "Matthieu Moy"
>>
>> I don't think you will find a name that fits all use-cases. IHMO, best
>> is to pick one rather general use-case, make the explanations for it,
>> and maybe explain somewhere that there are variants.
>>
>> If the fork is completely private, th
From: "Matthieu Moy"
Jordan DE GEA writes:
Matthieu Moy a écrit :
That is technically correct, but to illustrate the overall flow, I'd
rather avoid naming the repositories in terms of git commands. If you do
so, you will probably end up with tautological explanations like this
later in the
Jordan DE GEA writes:
>> Matthieu Moy a écrit :
>>
>> That is technically correct, but to illustrate the overall flow, I'd
>> rather avoid naming the repositories in terms of git commands. If you do
>> so, you will probably end up with tautological explanations like this
>> later in the text: "
> Matthieu Moy a écrit :
>
> That is technically correct, but to illustrate the overall flow, I'd
> rather avoid naming the repositories in terms of git commands. If you do
> so, you will probably end up with tautological explanations like this
> later in the text: "FETCH_REMOTE is the remote fr
From: "Junio C Hamano"
"Philip Oakley" writes:
That said, trying to find a good name for that 'third place' is not easy.
It's neither upstream, nor downstream (for Junio - the maintainer special
case - git.git would be his downstream). The me/git repo is like a
ferryman's landing across the o
"Philip Oakley" writes:
> That said, trying to find a good name for that 'third place' is not easy.
> It's neither upstream, nor downstream (for Junio - the maintainer special
> case - git.git would be his downstream). The me/git repo is like a
> ferryman's landing across the other side of the
>> Like PUSH_REMOTE, the remote where we fetch can be called FETCH_REMOTE.
>> e.g. That’s clear to say "I fetch from fetch_remote".
>>
>> Do you agree?
>
> That is technically correct, but to illustrate the overall flow, I'd
> rather avoid naming the repositories in terms of git commands. If yo
Jordan DE GEA writes:
> You’re right, finding a good name is not easy.
> Firstly, I wanted to use DOWNSTREAM and UPSTREAM. But git doesn’t make the
> difference between those words.
In english, "downstream" and "upstream" are relative terms. If A is
upstream compared to B, then B is downstre
> From: "Jordan DE GEA"
>> This document attempts to help you configure a Triangular Workflow.
>> +Here is an example of configuration:
>> +
>> +
>> + ---
>> +| UPSTREAM | maintainer | ORIGIN |
>
> UPSTREAM and ORIGIN a
[Just catching up with responses]
From: "Jordan DE GEA"
Sent: Tuesday, May 31, 2016 1:28 PM
Currently, Triangular Workflow can be configured, but there is no
Documentation about it. A documentation is useful to keep
configuration possibilities up-to-date.
The new documentation file gittriangula
On 05/31/2016 04:33 PM, Matthieu Moy wrote:
> Jordan DE GEA writes:
> [...]
>> +DESCRIPTION
>> +---
>> +
>> +Triangular Workflow (or Asymmetric Workflow) is a workflow which gives
>> +the possibility to:
>> +
>> +- fetch (or pull) from a repository
>> +- push to another repository
>
> [..
> Jordan DE GEA writes:
>> Currently, Triangular Workflow can be configured, but there is no
>> Documentation about it. A documentation is useful to keep
>> configuration possibilities up-to-date.
>
> You're using capitalization in a strange way. I don't think Triangular
> Workflow deserves to be
[ +Cc Michael Haggerty ]
Jordan DE GEA writes:
> Currently, Triangular Workflow can be configured, but there is no
> Documentation about it. A documentation is useful to keep
> configuration possibilities up-to-date.
You're using capitalization in a strange way. I don't think Triangular
Workflo
Currently, Triangular Workflow can be configured, but there is no
Documentation about it. A documentation is useful to keep
configuration possibilities up-to-date.
The new documentation file gittriangularworkflow explains
how to configure a triangular workflow.
Signed-off-by: Matthieu Moy
Signed-
17 matches
Mail list logo
