Re: git repo status change

2022-10-24 Thread accounts-gnunet
Thanks for that, I updated the branch with the make check fix from the other mailing list port. l On Mon, Oct 24, 2022 at 09:09:09AM +0200, Christian Grothoff wrote: > I've now updated the gnunet-ext build system, the example had not been > reasonably maintained in 10 years and was quite outdate

Re: git repo status change

2022-10-24 Thread Christian Grothoff
I've now updated the gnunet-ext build system, the example had not been reasonably maintained in 10 years and was quite outdated in various style points... -Christian On 10/24/22 03:05, Martin Schanzenbach wrote: Yeah I assume that, like gnunet.git, you'd want a .gitignore in m4/ containing l

Re: git repo status change

2022-10-23 Thread Martin Schanzenbach
Yeah I assume that, like gnunet.git, you'd want a .gitignore in m4/ containing libtool.m4 ltoptions.m4 ltsugar.m4 ltversion.m4 lt~obsolete.m4 wchar_t.m4 BR Martin On 22.10.22 16:59, accounts-gnu...@holbrook.no wrote: > > When I make changes to the gnunet-ext repo .h and .c files and build, the

git repo status change

2022-10-23 Thread accounts-gnunet
When I make changes to the gnunet-ext repo .h and .c files and build, the .m4 files also get part of the git delta. Is it supposed to be like this? -- $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add ..." to update w