News for hackers. Stuff that matters.
Re:I wrote a self-hosting C compiler in 40 days (2015) by walty8 on Thursday September 05, 2019 @10:08PM (#20892425)

  (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.
Re:I wrote a self-hosting C compiler in 40 days (2015) by rui314 on Thursday September 05, 2019 @10:19PM (#20892482)
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.
Re:I wrote a self-hosting C compiler in 40 days (2015) by CogitoCogito on Friday September 06, 2019 @04:59AM (#20894115)
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.

Re:I wrote a self-hosting C compiler in 40 days (2015) by saagarjha on Friday September 06, 2019 @02:54AM (#20893614)
Maybe you can disable git gc and allow for readers to grab a copy of your repository’s full reflog?
Re:I wrote a self-hosting C compiler in 40 days (2015) by rui314 on Friday September 06, 2019 @03:10AM (#20893670)
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.
Re:I wrote a self-hosting C compiler in 40 days (2015) by saagarjha on Friday September 06, 2019 @01:07PM (#20897452)
Fair point; I'm sure you can decide what kinds of things you think would be valuable to share.