3 ms·

(Actually in order to keep the commit history clean, I continue rewriting commit history and doing `git push -f`, actually I wonder if you might consider to m

by walty8 7y ago

(Actually in order to keep the commit history clean, I continue rewriting commit history and doing `git push -f`, actually I wonder if you might consider to maintain another clean repository. So there is a raw repository to record every real history, and a clean repositiory to for better reading? Because sometimes the raw history could be interesting too.

rui314 7y ago
I haven't considered that but I think that's hard to do for technical reasons. New commits are made on top of a clean history, so there's no single history of "raw" commits but they are intermingled.
- saagarjha 7y ago
  Maybe you can disable git gc and allow for readers to grab a copy of your repository’s full reflog?
  - rui314 7y ago
    I can disable gc, but reflog is really messy that I think no one can get any info from it. Even I can't, even though I know exactly what I did to the repo.
    - saagarjha 7y ago
      Fair point; I'm sure you can decide what kinds of things you think would be valuable to share.
- CogitoCogito 7y ago
  I would recommend you keep doing it the way you are. You are working on an educational exposition and choosing commits as part of that. You should take the position that the best judge of proper presentation. That said you could always turn off gc if some people want it, but I wouldn't put any more than a token effort into keeping that history.