Thanks Rong for updating the wiki pages.
Best,
Jark
> 在 2019年10月7日，18:37，Till Rohrmann 写道：
>
> Thanks for updating the wiki pages Rong. Looks good to me.
>
> Cheers,
> Till
>
> On Sun, Oct 6, 2019 at 7:21 PM Rong Rong wrote:
>
>> Thanks everyone for the suggestions. I think the majority
Thanks for updating the wiki pages Rong. Looks good to me.
Cheers,
Till
On Sun, Oct 6, 2019 at 7:21 PM Rong Rong wrote:
> Thanks everyone for the suggestions. I think the majority of us voted for
> using Github repo.
>
> I have updated the merging pull request wiki page [1] with the new
>
Thanks everyone for the suggestions. I think the majority of us voted for
using Github repo.
I have updated the merging pull request wiki page [1] with the new
instructions.
In addition, I have also added some general information I found useful when
setting up my committer account [2], including
Thanks Rong for volunteering. From my side +1 for using Github repo.
Cheers,
Till
On Fri, Sep 27, 2019 at 9:58 PM Thomas Weise wrote:
> +1 for recommendation to use the github repo
>
> Thanks,
> Thomas
>
> On Fri, Sep 27, 2019 at 9:29 AM Rong Rong wrote:
>
> > +1 on to state with one
+1 for recommendation to use the github repo
Thanks,
Thomas
On Fri, Sep 27, 2019 at 9:29 AM Rong Rong wrote:
> +1 on to state with one recommendation method in the wiki.
> I haven't encountered this often, so I do not have a preference regarding
> which way to go (Gitbox or Github). However,
+1 on to state with one recommendation method in the wiki.
I haven't encountered this often, so I do not have a preference regarding
which way to go (Gitbox or Github). However, I've experienced some
different issues on both Github and Gitbox when setting up new committer
credentials.
If
+1 to sticking with Github repo.
I have encountered once that pushing to ASF repo is blocked in China, but
GitHub always works for me and has better performance.
And this keeps the awesome green button for merging PRs from GitHub UI.
Best,
Jark
On Wed, 25 Sep 2019 at 15:57, Till Rohrmann wrote:
I think it makes sense to state a recommendation in the wiki.
If we decide on something I would be in favour of pushing to Github because
settings credentials up (private keys and signing keys) can happen in one
place. Moreover, one can reuse these credentials to push to contributors PR
branches
Thanks everyone for sharing your practices! The problem seems to be gone as
usual and I am able to push to ASF repo.
Verified by ASF INFRA [1], it's indeed caused by the mixed push problem
that Fabian said. Quote from INFRA, "This issue can sometimes occur when
people commit conflicting branches
I met the same problem. Pushing to the GitHub repo directly works fine and
it seems will resync the two repos.
Best, Hequn
On Tue, Sep 24, 2019 at 4:59 PM Fabian Hueske wrote:
> Maybe it's a mix of pushing to the ASF repository and Github mirrors?
> I'm only pushing to the ASF repositories
Maybe it's a mix of pushing to the ASF repository and Github mirrors?
I'm only pushing to the ASF repositories (although not that frequently
anymore...).
Cheers, Fabian
Am Di., 24. Sept. 2019 um 10:50 Uhr schrieb Till Rohrmann <
trohrm...@apache.org>:
> Pushing directly to Github also works for
Pushing directly to Github also works for me without a problem.
Cheers,
Till
On Tue, Sep 24, 2019 at 10:28 AM Jark Wu wrote:
> Hi Bowen,
>
> I have also encountered this problem. I don't know how to fix this.
> But pushing to GitHub repo always works for me.
>
> Best,
> Jark
>
> On Tue, 24 Sep
Hi Bowen,
I have also encountered this problem. I don't know how to fix this.
But pushing to GitHub repo always works for me.
Best,
Jark
On Tue, 24 Sep 2019 at 06:05, Bowen Li wrote:
> Hi committers,
>
> Recently I've run a repo issue multiple times in different days. When I
> tried to push a
Hi committers,
Recently I've run a repo issue multiple times in different days. When I
tried to push a commit to master, git reports the following error:
```
remote: This repository has been locked due to synchronization issues:
remote: - /x1/gitbox/broken/flink.txt exists due to a previous
14 matches
Mail list logo
