Re: [PATCH v1] Configure Git contribution guidelines for github.com

Andreas Heiduk writes: > Am 15.06.2017 um 18:43 schrieb Junio C Hamano: >> Another thing that may regress that you did not mention is that we >> would lose a convenient way to _count_ proposed changes coming via >> submitGit (i.e. you can simply go to the pull-request page),

Re: [PATCH v1] Configure Git contribution guidelines for github.com

Am 15.06.2017 um 18:43 schrieb Junio C Hamano: > Another thing that may regress that you did not mention is that we > would lose a convenient way to _count_ proposed changes coming via > submitGit (i.e. you can simply go to the pull-request page), so that > the number can be compared with the

Re: [PATCH v1] Configure Git contribution guidelines for github.com

Ævar Arnfjörð Bjarmason writes: > There are things we get out of this that would regress if > submitGit were changed this way: > > * Now when you submit a pull request you get a Travis build for > git/git, I don't get this if I push to any random branch in my > avar/git, and

Re: [PATCH v1] Configure Git contribution guidelines for github.com

On Mon, Jun 12, 2017 at 5:52 PM, Junio C Hamano wrote: > "Philip Oakley" writes: > >> From: "Lars Schneider" >>> Many open source projects use github.com for their contribution process. >>> Although we mirror the Git core

Re: [PATCH v1] Configure Git contribution guidelines for github.com

> On 10 Jun 2017, at 03:51, Junio C Hamano wrote: > > Jonathan Nieder writes: > >> Lars Schneider wrote: >> >>> Many open source projects use github.com for their contribution process. >>> Although we mirror the Git core repository to github.com [1] we

Re: [PATCH v1] Configure Git contribution guidelines for github.com

> On 10 Jun 2017, at 09:35, Jeff King wrote: > > On Fri, Jun 09, 2017 at 10:03:57AM -0700, Jonathan Nieder wrote: > >> Would putting a PULL_REQUEST_TEMPLATE and CONTRIBUTING in the >> top-level directory work? If I'm reading >>

Re: [PATCH v1] Configure Git contribution guidelines for github.com

> On 10 Jun 2017, at 14:48, Philip Oakley wrote: > > From: "Lars Schneider" >> Many open source projects use github.com for their contribution process. >> Although we mirror the Git core repository to github.com [1] we do not >> use any other

Re: [PATCH v1] Configure Git contribution guidelines for github.com

> On 12 Jun 2017, at 17:52, Junio C Hamano wrote: > > "Philip Oakley" writes: > >> From: "Lars Schneider" >>> Many open source projects use github.com for their contribution process. >>> Although we mirror the Git core

Re: [PATCH v1] Configure Git contribution guidelines for github.com

"Philip Oakley" writes: > From: "Lars Schneider" >> Many open source projects use github.com for their contribution process. >> Although we mirror the Git core repository to github.com [1] we do not >> use any other github.com service. This is

Re: [PATCH v1] Configure Git contribution guidelines for github.com

From: "Lars Schneider" Many open source projects use github.com for their contribution process. Although we mirror the Git core repository to github.com [1] we do not use any other github.com service. This is unknown/unexpected to a number of (potential) contributors

Re: [PATCH v1] Configure Git contribution guidelines for github.com

On Fri, Jun 09, 2017 at 10:03:57AM -0700, Jonathan Nieder wrote: > Would putting a PULL_REQUEST_TEMPLATE and CONTRIBUTING in the > top-level directory work? If I'm reading > https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file > correctly

Re: [PATCH v1] Configure Git contribution guidelines for github.com

Jonathan Nieder writes: > Lars Schneider wrote: > >> Many open source projects use github.com for their contribution process. >> Although we mirror the Git core repository to github.com [1] we do not >> use any other github.com service. This is unknown/unexpected to a >>

Re: [PATCH v1] Configure Git contribution guidelines for github.com

Ævar Arnfjörð Bjarmason writes: > On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider > wrote: > ... >> I am perfectly aware that adding a ".github" directory in the Git core >> tree is ugly. However, I believe the benefits ("well informed new >>

Re: [PATCH v1] Configure Git contribution guidelines for github.com

Hi, Some mostly nitpicky initial thoughts. Thanks for writing this. Lars Schneider wrote: > Many open source projects use github.com for their contribution process. > Although we mirror the Git core repository to github.com [1] we do not > use any other github.com service. This is

Re: [PATCH v1] Configure Git contribution guidelines for github.com

> On 09 Jun 2017, at 18:18, Ævar Arnfjörð Bjarmason wrote: > > On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider > wrote: >> Many open source projects use github.com for their contribution process. >> Although we mirror the Git core repository to

Re: [PATCH v1] Configure Git contribution guidelines for github.com

On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider wrote: > Many open source projects use github.com for their contribution process. > Although we mirror the Git core repository to github.com [1] we do not > use any other github.com service. This is unknown/unexpected to a >