Re: This repository is currently out of sync, please

Hi Okay INFRA fixed the gitbox issue and it works again. In the mean time I have checked out from github directly and that worked also for me. On Wed, Oct 25, 2017 at 9:16 PM, Claus Ibsen wrote: > Hi > > Yeah I just tried upgrading to latest git client 2.14.1 > And then

Re: This repository is currently out of sync, please

Hi Yeah I just tried upgrading to latest git client 2.14.1 And then also a fresh git clone from the gitbox url. All of that fails. Now I am moving to pure github - then I can be a young hipster too On Wed, Oct 25, 2017 at 9:13 PM, Luca Burgazzoli wrote: > Hi Claus, >

Re: This repository is currently out of sync, please

Hi Claus, sorry I did test against github before and yeah, if pushing to gitbox I have a similar issue: Counting objects: 5, done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 1.09 KiB | 1.09 MiB/s, done. Total 5 (delta 4), reused 0

Re: This repository is currently out of sync, please

Hi Luca Thanks for the tip. I had matching before, but it still fails [push] default = matching But it works for you. Maybe I do as anyone else learning git, copy your changed stuff somewhere else, and delete everything and start all over again ;) On Wed, Oct 25, 2017 at 8:55 PM, Luca

Re: This repository is currently out of sync, please

Don't have the same issue, maybe you just need to add [push] default = simple to your .gitconfig --- Luca Burgazzoli On Wed, Oct 25, 2017 at 8:35 PM, Claus Ibsen wrote: > Hi > > I logged a ticket at INFRA > https://issues.apache.org/jira/browse/INFRA-15372 > > On

Re: This repository is currently out of sync, please

Hi I logged a ticket at INFRA https://issues.apache.org/jira/browse/INFRA-15372 On Wed, Oct 25, 2017 at 5:54 PM, Claus Ibsen wrote: > Hi > > Do others get this error when attempting to push to Apache git? > > It used to work today, but in the last hour or so I get this

R: This repository is currently out of sync, please

Maybe you can try directly on github repo and see if it works Inviato da Yahoo Mail su Android Il mer, 25 ott, 2017 alle 17:55, Claus Ibsen ha scritto: Hi Do others get this error when attempting to push to Apache git? It used to work today, but in the last hour

Re: About contributions without documentation

Am 25.10.2017 um 08:55 schrieb Claus Ibsen: we should start to be insisting on requiring documentation updates from contributions that come to us via github PRs or patch files to JIRA. Now there is no excuse we have the means to document directly with the source code. +1

R: This repository is currently out of sync, please

I cannot try right now. Do we need to contact infra? Inviato da Yahoo Mail su Android Il mer, 25 ott, 2017 alle 17:55, Claus Ibsen ha scritto: Hi Do others get this error when attempting to push to Apache git? It used to work today, but in the last hour or so I

This repository is currently out of sync, please

Hi Do others get this error when attempting to push to Apache git? It used to work today, but in the last hour or so I get this error. davsclaus:/Users/davsclaus/workspace/camel/components/camel-kafka (master)/$ git push origin Counting objects: 43, done. Delta compression using up to 8

[GitHub] camel pull request #2060: CAMEL-11292: Upgrade to scala 2.12.x

GitHub user sinwe opened a pull request: https://github.com/apache/camel/pull/2060 CAMEL-11292: Upgrade to scala 2.12.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/sinwe/camel master Alternatively you can review and apply

[GitHub] camel pull request #2059: [CAMEL-11946] Invalid artifactId in docs for camel...

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2059 ---

[GitHub] camel pull request #2059: [CAMEL-11946] Invalid artifactId in docs for camel...

GitHub user tdiesler opened a pull request: https://github.com/apache/camel/pull/2059 [CAMEL-11946] Invalid artifactId in docs for camel-json-validator You can merge this pull request into a Git repository by running: $ git pull https://github.com/tdiesler/camel CAMEL-11946

[GitHub] camel pull request #2058: CAMEL-11944: Ensure HBaseConfiguration ClassLoader...

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2058 ---

[GitHub] camel pull request #2058: CAMEL-11944: Ensure HBaseConfiguration ClassLoader...

GitHub user jamesnetherton opened a pull request: https://github.com/apache/camel/pull/2058 CAMEL-11944: Ensure HBaseConfiguration ClassLoader is set correctly You can merge this pull request into a Git repository by running: $ git pull https://github.com/jamesnetherton/camel

[GitHub] camel pull request #2057: upgrade to pubnub 4.13.0

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2057 ---

About contributions without documentation

Hi Now that all components, data formats, languages etc are documented with the source code and they have adoc files in the src/main/docs folder, we should start to be insisting on requiring documentation updates from contributions that come to us via github PRs or patch files to JIRA. In the