* MELPA and rewriting history for the (git) repo
@ 2016-02-11 10:29 Uwe Brauer
2016-02-12 14:08 ` Phillip Lord
0 siblings, 1 reply; 3+ messages in thread
From: Uwe Brauer @ 2016-02-11 10:29 UTC (permalink / raw)
To: emacs-devel
Hi
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MELPA and rewriting history for the (git) repo
2016-02-11 10:29 MELPA and rewriting history for the (git) repo Uwe Brauer
@ 2016-02-12 14:08 ` Phillip Lord
2016-02-13 2:46 ` Alex Dunn
0 siblings, 1 reply; 3+ messages in thread
From: Phillip Lord @ 2016-02-12 14:08 UTC (permalink / raw)
To: emacs-devel
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 <oub@mat.ucm.es> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MELPA and rewriting history for the (git) repo
2016-02-12 14:08 ` Phillip Lord
@ 2016-02-13 2:46 ` Alex Dunn
0 siblings, 0 replies; 3+ messages in thread
From: Alex Dunn @ 2016-02-13 2:46 UTC (permalink / raw)
To: Phillip Lord, emacs-devel
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 <phillip.lord@russet.org.uk> 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 <oub@mat.ucm.es> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-13 2:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-11 10:29 MELPA and rewriting history for the (git) repo Uwe Brauer
2016-02-12 14:08 ` Phillip Lord
2016-02-13 2:46 ` Alex Dunn
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).