[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MELPA and rewriting history for the (git) repo
From: |
Alex Dunn |
Subject: |
Re: MELPA and rewriting history for the (git) repo |
Date: |
Fri, 12 Feb 2016 18:46:01 -0800 |
User-agent: |
Notmuch/0.21 (http://notmuchmail.org) Emacs/25.0.90.1 (x86_64-apple-darwin15.3.0) |
It does a fetch and then a hard reset, so there shouldn’t be problems
with history being rewritten:
https://github.com/melpa/melpa/blob/master/package-build.el#L551-L561
There could be problems for MELPA Stable if the new history has tags
that are parsed as an earlier version; that currently requires manual
intervention (https://github.com/melpa/melpa/pull/3362#issuecomment-173058525).
Phillip Lord <address@hidden> writes:
> For MELPA, I don't think it would make any difference -- I think, it
> just looks for changes in the hash and if it sees one generates the
> latest version. It might cause a problem if it uses git update, rather
> than a fresh clone for each checkout.
>
> There are many good reasons not to rebase master, though.
>
>
> Uwe Brauer <address@hidden> writes:
>> Matlab-emacs has moved to a git repo at SF and MELPA points now to that
>> repo.
>>
>>
>> The question is this: git allows to rewrite history but usually
>> for a public repo, it is strong advised in the documentation, not to do
>> so.
>>
>> What would happen with the corresponding MELPA packages, if one rewrote
>> the history?
>>
>> Thanks
>>
>> Uwe Brauer