Hi, Leo Famulari <l...@famulari.name> writes:
> On Thu, Feb 06, 2025 at 12:08:22PM -0800, Vagrant Cascadian wrote: >> > All these commits before v0.16 could be archived. And the “new” >> > repository would start at this 4a0b87f0ec5b6c2dcf82b372dd20ca7ea6acdd9c. >> > >> > This would save some resource that are downloaded for nothing at the >> > first “guix pull”. >> > >> > Well, for some files, ’git blame’ and ’git log’ would be “broken” but if >> > I count the number of times that I dug the history before 2019, it would >> > not be an issue for me to use another archived / separated repository. >> >> Maybe I misunderstand, but can that be done without rewriting history, >> which would break the chain of signed commits? That would seem like a >> great time to introduce malicious code... > > Let's break this into a different proposal, and look into shallow > cloning. I don't think there is anything exceptional about or repo that > makes this urgent. I wouldn't want to work on a repo which has its pre 2019 history unavailable. I'm a heavy user of 'git blame' and having the full history is precious to me. So yeah, I second shallow cloning as a better option to look into. -- Thanks, Maxim
