hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley" <omal...@apache.org>
Subject Re: [NOTICE] Rewriting master branch in git
Date Mon, 30 Nov 2015 23:55:11 GMT
Ok, the branches have been moved and we should be good to go.

.. Owen

On Mon, Nov 30, 2015 at 11:44 AM, Owen O'Malley <omalley@apache.org> wrote:

> All,
>    As many of you have noticed, we've had a commit on the master branch
> that accidentally included a 103MB tarball in the commit. The tarball was
> removed a few commits later, but the presence of the offending commit has
> blocked us from pushing to repository clones on Github, because they have a
> file limit of 100MB. That has made Hive's master branch difficult to work
> with.
>
>   We are in the process of removing the file from the git history that is
> part of the master branch. There will be a tag (master_2015_11_30) at the
> previous head of the master branch and master will have the new commit
> history.
>
>   The diff between the two commits is empty and thus it is easy to
> cherry-pick (or rebase) a range of commits between the two histories.
>
> Thanks,
>    Owen
>
> The original problematic commit: 5feb58db2c9
> The deletion of the large tarball: 7519ff6ab4
>
> Current head of master: 0a96201f268a
> Current head of master-fixed: e325eac9f6ee
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message