Re: contributing

[accounts-gnunet]

Hmm, the format-patch command does not preserve signatures.

Anyway, here is a patch for my workaround to be able to build and run
gnunet extension when installing in a non-standard path. Without this,
the extension would derive the config path from the location of the
binary ($PREFIX/lib/gnunet/libexec).

Also, a slight edit in test to make make check work again.



On Tue, Oct 25, 2022 at 07:27:45PM +0100, madmurphy wrote:
> On Tue, Oct 25, 2022 at 6:28 PM <accounts-gnunet@holbrook.no> wrote:
> 
> I would like to send some code amendments to the gnunet-ext repo. What are
> the necessary steps, please?
> 
> The easieast way:
> 
> git clone https://git.gnunet.org/gnunet-ext.git
> cd gnunet-ext
> 
> Edit whatever you want to edit in the gnunet-ext directory, then launch the
> following commands (feel free to change the message as it best suits you):
> 
> git add --all
> git commit -m 'Write your message here'
> git format-patch -1
> 
> Finally, send the 0001-Write-your-message-here.patch file generated to this
> mailing list (the actual name will change according to your message).
> 
> --madmurphy
> 
> On Tue, Oct 25, 2022 at 6:28 PM <accounts-gnunet@holbrook.no> wrote:
> 
> > Hello,
> >
> > there's still TODO wtr link to copyright waiver for contributing in the
> > docs:
> >
> >
> > file:///home/lash/src/build/gnunet/0.17.6-198-g1436e4266/doc/handbook/html/developers/contributing.html
> >
> > I would like to send some code amendments to the gnunet-ext repo. What
> > are the necessary steps, please?
> >
> > Thanks,
> > l
> >

0001-Rehabilitate-test-and-non-standard-build-location.patch
Description: Text document

signature.asc
Description: PGP signature