Re: MELPA and rewriting history for the (git) repo

[Phillip Lord]

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