-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libxo support for devinfo (take 2) #1480
base: main
Are you sure you want to change the base?
Conversation
I'm learning about git rebase --interactive. Hold your horses. |
b87feb1
to
72fe367
Compare
e3eff60
to
6ed19d7
Compare
e9b3034
to
3a48c3e
Compare
0043583
to
5d33dcd
Compare
OK. That's this round. It looks to be mostly style. I'll test it on the next round to see if I can find some issues I'm not seeing in glancing over this. |
Also, the 3rd-5th commit messages need to have more descriptive titles. They are a little generic. Let me know if you want more specific suggestions. |
68f708d
to
3967d4e
Compare
Other than a couple of very minor style nits, the only thing I see is the strdup/refactoring suggestion I made. |
1cdf3cc
to
6c7898e
Compare
When libxo is added we want the whole indentation to be printed in a single call. Otherwise the html will be spammed with indentation tags.
6017e95
to
6038baa
Compare
…ture No functional change intended.
2f50035
to
a0456b0
Compare
No functional change intended.
We'll need it twice when libxo is added. No functional change intended.
The code will diverge when libxo is added.
No functional change intended.
This is prep for libxo. No functional change intended.
This is prep for libxo. No functional change intended.
No functional change intended.
This is prep for libxo. No functional change intended.
This is prep for libxo. No functional change intended.
Since last time I have
Many of the prep changes only makes sense once libxo are added.
I had to do quite a few contortions to retrofit libxo into this thing.