Git Product home page Git Product logo

Comments (5)

newren avatar newren commented on July 17, 2024 1

Yeah, making people go through repeated history rewrites sounds very problematic, and it is also a bad idea to just push a rewrite without informing other people using the repo. It's a big flag day event kind of thing. Your new plan sounds like a better idea, but you'll still need to be careful to coordinate with folks so that they don't keep adding to directories that you have extracted in the mean time or you'll risk losing those changes when you do the final cutover.

Yes, coordination is painful and history rewrites requiring them can thus be very painful. But the need behind such coordination was totally part of the design goals behind git; they wanted to prevent situations where someone just broke into the server and modified history and no one was any the wiser when folks tried to download updates. The reason they designed for such a scenario was that someone tried this exact thing with the linux kernel before git was invented -- and the perpetrator would have succeeded had the kernel been using cvs or svn, but the problem was noticed due to some integrity checks that bitkeeper performed.

from git-filter-repo.

newren avatar newren commented on July 17, 2024

Have you read https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#DISCUSSION, particular the parts about "recovering from upstream rebase" and item 4?

from git-filter-repo.

newren avatar newren commented on July 17, 2024

I'll go ahead and close this, assuming the links above answered the question. Let me know if you have further questions about this, though.

from git-filter-repo.

m1nkeh avatar m1nkeh commented on July 17, 2024

Oops, apologies, didn't see the earlier reply!

I shall review 🙂

from git-filter-repo.

m1nkeh avatar m1nkeh commented on July 17, 2024

Have you read https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#DISCUSSION, particular the parts about "recovering from upstream rebase" and item 4?

Right, given that a reply, and i am concluding that what i am considering is quite a bad idea? 😉

The use case I am trying to cater for here is (re)moving sections of my target repo in to other ones a piece at a time over a period of weeks.. so what i'll probably do is just script what i want to move to new repos, run that over a few days, and then when done invert all the commands on the original repo and push somewhere new.

Ty.

from git-filter-repo.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.