Re: Question about tracking files, and Doxygen updates.

> On 26. Aug 2022, at 23:41, Willow Liquorice <[email protected]> wrote:
> 
> Hello again,
> 
> I've put a .gitignore in doc/doxygen on my local dev/willow/doxygen, so the Doxygen output (along with other autogenerated files) doesn't get tangled up in the git history. Should .gitignore include gnunet.tag too?

I'm not sure what that file does. But I guess, yes.

> 
> I've got a good workflow for stripping redundant doc comments in Neovim. I've already put a dent in the number of warnings doxygen spits out in the day or two since I cracked it. There are notes on that workflow in contrib/warningfilter.py on my local branch.
> 
> I also hacked Makefile.am and the doxyfile to automate updating PROJECT_NUMBER, so you can look forward to that too once I've tidied up
> the branch. It's a bit inelegant but it gets the job done.
> 

Please keep in mind to work on new branches, i.e. not branches I already merged.
Because they would require a new rebase and I am not sure atm if you branches currently diverge from what is online.

Thanks!

BR

> Best wishes,
> 	Willow
>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPREGPBD5jRS9JNFHCwmY74b1m2oFAmMKB7EACgkQCwmY74b1
m2p4kQ/8C+rxHrFYUhbg3qYmEjYftU83FuZVwSD0tlhcukl2/yevWYTkpbEm2cm1
OQ2d4ND2Xr0+PrEhssBgWnBKb2umMPZbjI3HoUW1sxjquSqVIVrWRnzFMalofapw
R+SwlAt7bP+nJ0EyYeIFmNYcfiPWmxPCNpt6WHp5kS9VH70dC5OJBy4eWgMgs/UD
ZEg9j6Dp6/w/EyuzVoRF3zCs1i5jNtcKclq1Hf1OQ80SRcX+WX1O7s33oMgRqbaW
323A8vO3B27Jthod8k6BQXYgMzXDYFbAsJG8QWzTnjbumcveUpv44OwAVz5n+IlJ
xxNKtS8E31AGqvr8xgzmN3shWJFZ/vOZFuX3ik+ieaQPFAtRnSv/GSH54ELIn3+P
taSecrjxEs2zQSgsQGGWE1SvTKRSOBzPKVGE2CueFWHVoZYQZfoj9GAAapBMZQaO
Q9bxTQTNHXmQdI/9wyb+M/GpjECpXHtwUmO8Y4t8g4vqf5inZ7BiqSUxyzHWqknv
8hqWsm0+hORMmFVHD9NqwiQZ2poyp9qPyZFvw04vO0Bzj8sjGtg9h7n4dxTbXjsw
nqK1ubawnnzxI2kg9fR9x6cHe67JT9LJCemePzkBtDUxHOHs6a48LP7aSZvNzaVG
6JQEXBByDXVC1tX0ZFVZhAH0CqPZBYa7rIB2Ng5w+YHwsIE84E8=
=N/Vr
-----END PGP SIGNATURE-----