This vote passes with 7 +1s and no -1s. I'll update infra that we're ready
to do this.
On 23 April 2018 at 02:37, Gilles wrote:
> On Sun, 22 Apr 2018 14:11:46 -0500, Matt Sicker wrote:
>
>> An example project already using gitbox is whimsy:
>>
On Sun, 22 Apr 2018 14:11:46 -0500, Matt Sicker wrote:
An example project already using gitbox is whimsy:
https://github.com/apache/whimsy
And "Commons Geometry":
https://gitbox.apache.org/repos/asf?p=commons-geometry.git
Commits were pushed to that "remote".
Gilles
On 22 April 2018 at
An example project already using gitbox is whimsy:
https://github.com/apache/whimsy
On 22 April 2018 at 14:06, ajs6f wrote:
> I have asked INFRA about this (for another project) and they confirmed
> that GitBox runs the mirroring Github => Apache, so that PRs can be merged
>
I have asked INFRA about this (for another project) and they confirmed that
GitBox runs the mirroring Github => Apache, so that PRs can be merged at
Github. I did not ask about whether commits can also be pushed directly to
Apache.
ajs6f
> On Apr 22, 2018, at 3:03 PM, Matt Sicker
On 22 April 2018 at 13:34, Ralph Goers wrote:
> For example, with GitBox can we now merge pull requests directly at
> GitHub? That would be a nice benefit. Can we still commit to the ASF git
> repo or only at GitHub?
>
>From my understanding, you can merge PRs
On 2018-04-22, Matt Sicker wrote:
> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to
+1
Although I really would like to see documentation somewhere on how the process
differs. For example, with GitBox can we now merge pull requests directly at
GitHub? That would be a nice benefit. Can we still commit to the ASF git repo
or only at GitHub?
Ralph
> On Apr 22, 2018, at 10:07
+1
Oliver
Am 22.04.2018 um 19:07 schrieb Matt Sicker:
> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it
+1
> On Apr 22, 2018, at 1:21 PM, Gary Gregory wrote:
>
> +1
>
> Gary
>
>> On Sun, Apr 22, 2018, 11:07 Matt Sicker wrote:
>>
>> This is a vote to migrate existing Git repositories from the old git-wip-us
>> infrastructure to the new gitbox
+1
Gary
On Sun, Apr 22, 2018, 11:07 Matt Sicker wrote:
> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use
+1
Le 22 avr. 2018 19:10, "Pascal Schumacher" a
écrit :
> +1
>
> Am 22.04.2018 um 19:07 schrieb Matt Sicker:
>
>> This is a vote to migrate existing Git repositories from the old
>> git-wip-us
>> infrastructure to the new gitbox infrastructure. New Apache projects are
+1
Am 22.04.2018 um 19:07 schrieb Matt Sicker:
This is a vote to migrate existing Git repositories from the old git-wip-us
infrastructure to the new gitbox infrastructure. New Apache projects are
not allowed to use git-wip-us and are instead directed to use gitbox. As
such, it makes sense for
This is a vote to migrate existing Git repositories from the old git-wip-us
infrastructure to the new gitbox infrastructure. New Apache projects are
not allowed to use git-wip-us and are instead directed to use gitbox. As
such, it makes sense for us to stay consistent with other projects.
The
13 matches
Mail list logo