You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Chris Hostetter <ho...@fucit.org> on 2017/03/03 21:13:52 UTC
Re: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
WTF happened here????
1) Did we lose anything ?
... IIUC we only lost one commit (which Noble did again?)
2) I thought the main apache repo was configured to reject forced
pushes????
: Date: Thu, 2 Mar 2017 11:09:37 +0000 (UTC)
: From: noble@apache.org
: Reply-To: dev@lucene.apache.org
: To: commits@lucene.apache.org
: Subject: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
:
: Repository: lucene-solr
: Updated Branches:
: refs/heads/branch_6x 84a7470f4 -> a607a2c6c (forced update)
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
Posted by Noble Paul <no...@gmail.com>.
Yeah, it was an accidental merge commit which I had to revert. Hope
everything is alright
On Sat, Mar 4, 2017 at 9:50 AM, Chris Hostetter <ho...@fucit.org>
wrote:
> : > WTF happened here????
> : >
> : > 1) Did we lose anything ?
> : > ... IIUC we only lost one commit (which Noble did again?)
> :
> : IIUIC the only way to be sure is to compare the history from someone’s
> : local repo that still hasn’t been updated with the (possibly) truncated
> : history from GitHub.
>
> Assuming we trust the commit emails, I think only 1 commit was lost, and
> it looks like it was nobles ...
>
> ...
> smiley (e51e50e55 -> a607a2c6c) # A6...
> noble (a607a2c6c -> 84a7470f4)
> noble (84a7470f4 -> a607a2c6c) FORCED BACK TO 'A6...'
> noble (a607a2c6c -> dea29d12f)
> jpountz (dea29d12f -> 780690b1e)
> ...
>
> ...so maybe this was intentional to fix a mistake?
>
> still seems like a risky fucking thing to allow in our repo...
>
> : > 2) I thought the main apache repo was configured to reject forced
> : > pushes????
> :
> : THIS ^^^ apparently it isn’t. INFRA-13613.
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
-----------------------------------------------------
Noble Paul
Re: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
Posted by Chris Hostetter <ho...@fucit.org>.
: > WTF happened here????
: >
: > 1) Did we lose anything ?
: > ... IIUC we only lost one commit (which Noble did again?)
:
: IIUIC the only way to be sure is to compare the history from someone\u2019s
: local repo that still hasn\u2019t been updated with the (possibly) truncated
: history from GitHub.
Assuming we trust the commit emails, I think only 1 commit was lost, and
it looks like it was nobles ...
...
smiley (e51e50e55 -> a607a2c6c) # A6...
noble (a607a2c6c -> 84a7470f4)
noble (84a7470f4 -> a607a2c6c) FORCED BACK TO 'A6...'
noble (a607a2c6c -> dea29d12f)
jpountz (dea29d12f -> 780690b1e)
...
...so maybe this was intentional to fix a mistake?
still seems like a risky fucking thing to allow in our repo...
: > 2) I thought the main apache repo was configured to reject forced
: > pushes????
:
: THIS ^^^ apparently it isn\u2019t. INFRA-13613.
-Hoss
http://www.lucidworks.com/
Re: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
Posted by Andrzej Białecki <ab...@sigram.com>.
> On 3 Mar 2017, at 22:13, Chris Hostetter <ho...@fucit.org> wrote:
>
>
> WTF happened here????
>
> 1) Did we lose anything ?
> ... IIUC we only lost one commit (which Noble did again?)
IIUIC the only way to be sure is to compare the history from someone’s local repo that still hasn’t been updated with the (possibly) truncated history from GitHub.
>
> 2) I thought the main apache repo was configured to reject forced
> pushes????
THIS ^^^ apparently it isn’t. INFRA-13613.
>
>
> : Date: Thu, 2 Mar 2017 11:09:37 +0000 (UTC)
> : From: noble@apache.org
> : Reply-To: dev@lucene.apache.org
> : To: commits@lucene.apache.org
> : Subject: [lucene-solr] Git Push Summary [forced push!] [Forced Update!]
> :
> : Repository: lucene-solr
> : Updated Branches:
> : refs/heads/branch_6x 84a7470f4 -> a607a2c6c (forced update)
> :
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
Andrzej Białecki
ab@sigram.com