Moving to the obsolete repo
2 views
Skip to first unread message
Ron Kaplan
Apr 17, 2026, 11:50:35 AMApr 17
to Medley Interlisp core
What's the command/procedure for moving from Medley (or anywhere) to Obsolete? Should GITFNS include a way of doing that?
Nick Briggs
Apr 17, 2026, 12:08:23 PMApr 17
to Ron Kaplan, Lisp Core
It's not easy to move files between repositories if you want to retain the history from the source repo in the destination repo.
You end up making a new local copy of the source repository,
using git filter-repo to delete everything in the repository that *isn't* what you want to move,
add the mostly empty local copy as a new remote for the destination (obsolete) repository,
fetch that remote into the destination,
then merge it with the "--allow-unrelated-histories" flag,
then remove the new remote from the destination repository
then check again that everything actually worked before pushing the destination (obsolete) repo back to github
and deleting the new local copy of the source repo (important! you don't want to push that back overwriting the real repo)
I wouldn't trust this to be scripted - it really needs a person looking at the result of every git operation to check that what happened happened correctly.
> On Apr 17, 2026, at 08:50, Ron Kaplan <ron.k...@post.harvard.edu> wrote:
>
> What's the command/procedure for moving from Medley (or anywhere) to Obsolete? Should GITFNS include a way of doing that?
>
> --
> You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/lispcore/E0C1124C-D7B7-4479-BF38-514F1F2308D5%40post.harvard.edu.
You end up making a new local copy of the source repository,
using git filter-repo to delete everything in the repository that *isn't* what you want to move,
add the mostly empty local copy as a new remote for the destination (obsolete) repository,
fetch that remote into the destination,
then merge it with the "--allow-unrelated-histories" flag,
then remove the new remote from the destination repository
then check again that everything actually worked before pushing the destination (obsolete) repo back to github
and deleting the new local copy of the source repo (important! you don't want to push that back overwriting the real repo)
I wouldn't trust this to be scripted - it really needs a person looking at the result of every git operation to check that what happened happened correctly.
> On Apr 17, 2026, at 08:50, Ron Kaplan <ron.k...@post.harvard.edu> wrote:
>
> What's the command/procedure for moving from Medley (or anywhere) to Obsolete? Should GITFNS include a way of doing that?
>
> You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/lispcore/E0C1124C-D7B7-4479-BF38-514F1F2308D5%40post.harvard.edu.
Ron Kaplan
Apr 17, 2026, 12:42:18 PMApr 17
to Nick Briggs, Lisp Core
If this is what is required to maintain the history, I don't think it's worth it. The history is still somewhere in the source repository, if anybody really needed to find it.
So I think that I would just do the obvious thing, without getting GITFNS involved: Copy the file from the Medley clone to the Obsolete clone, delete the file from the Medley clone, push both.
So I think that I would just do the obvious thing, without getting GITFNS involved: Copy the file from the Medley clone to the Obsolete clone, delete the file from the Medley clone, push both.
Reply all
Reply to author
Forward
0 new messages