You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "David Nalley (JIRA)" <ji...@apache.org> on 2015/01/17 22:48:34 UTC
[jira] [Commented] (INFRA-9034) Sqoop git repository is missing
commits after the transition to new host
[ https://issues.apache.org/jira/browse/INFRA-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281566#comment-14281566 ]
David Nalley commented on INFRA-9034:
-------------------------------------
Thank's for catching this.
I've made the git repo for sqoop read-only for the time being, until we understand why there is a distinction.
[~pctony] Please make this a priority when you come online.
> Sqoop git repository is missing commits after the transition to new host
> ------------------------------------------------------------------------
>
> Key: INFRA-9034
> URL: https://issues.apache.org/jira/browse/INFRA-9034
> Project: Infrastructure
> Issue Type: Bug
> Components: Git
> Reporter: Jarek Jarcec Cecho
> Priority: Blocker
>
> I’ve noticed that we are missing several commits in our repositories. For example here is top of the “trunk” branch on ASF [1] where last commit is from 2014-12-18. Here [2] is mirror of the official repository that for the same branch have last commit from 2015-01-06.
> Is this expected? Should we move to a different host?
> Links:
> 1: https://git-wip-us.apache.org/repos/asf?
> p=sqoop.git;a=shortlog;h=refs/heads/trunk
> 2: https://github.com/apache/sqoop/commits/trunk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)