Re: [PATCHv4] Documentation: triangular workflow

2016-06-13 Thread Junio C Hamano
"Philip Oakley" writes: > From: "Junio C Hamano" >> I do not think I agree. >> >> If you apriori know that you do want to hack on a project's code, then >> forking at GitHub first and then cloning the copy would be OK. > > You've clipped my other point: > > -One issue may be the differen

Re: [PATCHv4] Documentation: triangular workflow

2016-06-11 Thread Philip Oakley
From: "Ramkumar Ramachandra" Junio C Hamano wrote: Jordan DE GEA wrote: > +* Allows contributors to work with Git even though they do not have > +write access to **UPSTREAM**. > > +* Allows maintainers to receive code from contributors they may not > +trust. Triangular workflow is the abilit

Re: [PATCHv4] Documentation: triangular workflow

2016-06-11 Thread Philip Oakley
From: "Junio C Hamano" "Philip Oakley" writes: +Preparation +~~~ + +Cloning from **PUBLISH**, which is a fork of **UPSTREAM** or an empty +repository. I agree here. To clone the upstream, to which you have no push access (by definition), would leave the config badly mis-set for the

Re: [PATCHv4] Documentation: triangular workflow

2016-06-11 Thread Ramkumar Ramachandra
Junio C Hamano wrote: > Jordan DE GEA wrote: > > > +* Allows contributors to work with Git even though they do not have > > +write access to **UPSTREAM**. > > > > +* Allows maintainers to receive code from contributors they may not > > +trust. Triangular workflow is the ability to accept changes f

Re: [PATCHv4] Documentation: triangular workflow

2016-06-10 Thread Junio C Hamano
"Philip Oakley" writes: >> +Preparation >> +~~~ >> + >> +Cloning from **PUBLISH**, which is a fork of **UPSTREAM** or an empty >> +repository. > > I agree here. To clone the upstream, to which you have no push access (by > definition), would leave the config badly mis-set for the basic u

Re: [PATCHv4] Documentation: triangular workflow

2016-06-09 Thread Philip Oakley
From: "Jordan DE GEA" Currently, triangular workflow can be configured, but there is no documentation about it. A documentation is useful to keep configuration possibilities up-to-date. A new subsection is created in gitworkflow. Signed-off-by: Michael Haggerty Signed-off-by: Matthieu Moy Si

Re: [PATCHv4] Documentation: triangular workflow

2016-06-09 Thread Junio C Hamano
Jordan DE GEA writes: > +Motivations > +~~~ > +* Allows contributors to work with Git even though they do not have > +write access to **UPSTREAM**. > > +* Allows maintainers to receive code from contributors they may not > +trust. I somehow don't think "even though" sits well here. You

[PATCHv4] Documentation: triangular workflow

2016-06-09 Thread Jordan DE GEA
Currently, triangular workflow can be configured, but there is no documentation about it. A documentation is useful to keep configuration possibilities up-to-date. A new subsection is created in gitworkflow. Signed-off-by: Michael Haggerty Signed-off-by: Matthieu Moy Signed-off-by: Jordan DE GE