Conversation

Notices

1. Hallå Kitteh (clacke@social.heldscal.la)'s status on Wednesday, 30-Aug-2017 11:36:08 UTC Hallå Kitteh

   • Krzysztof Jurewicz
   @krzysiekj Yes. And it truncates the repo. If I have commit asdf1234 and I fetch --depth=1 asdf9876, which has asdf1234 as parent, it still says asdf9876 has no parent and asdf1234 becomes an orphaned commit, picked up at the next gc (unless it's directly by a branch or tag). Even though it's there in the repo, when you look at asdf9876 git will say the parent is not present.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 29-Aug-2017 11:26:11 UTC Hallå Kitteh
     I would be very happy to find some way to do --shallow without destroying existing commit relations.
     
     That's not a metaphor for anything. I'm talking about #git.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Wednesday, 30-Aug-2017 00:07:27 UTC Hallå Kitteh

     • Krzysztof Jurewicz
     @krzysiekj It adds grafts to truncate the chain. I just want it to download less, not disregard the parent if I happen to already have it.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Wednesday, 30-Aug-2017 11:41:58 UTC Hallå Kitteh

     in reply to
     Apparently I complained already two weeks ago. Still annoyed. :-)
     
     https://social.heldscal.la/notice/3393180