Hi Giuseppe, On Mon, 26 Sep 2016 10:23:31 +0200 Giuseppe Scrivano <gscriv...@gnu.org> wrote:
> Hi, > > Matthew White <mehw.is...@inventati.org> writes: > > >> Could you please re-send the updated series? > > > > You may find the series of patches in my branch > > https://github.com/mehw/wget/tree/metalink_staging . > > it works for me, I will take a look soon at them. I'm keeping the branch updated and rebased on the latest Savannah's master. > > > > > There's a new Metalink/XML v3 python class: > > * testenv/misc/metalinkv3_xml.py > > > > I still have to update the NEWS file. > > > >> > >> I had some problems applying your patches, as some comments from the > >> emails got into the patch itself, could you try with git send-email? > > > > About `git send-email`, what Subject, In-Reply-to, and References should be > > used to post the series of patches? > > you could use the subject to tag the new version of the series: like > "PATCH v2". In-reply-to and References should be empty for a new > version of a patch series. They are more helpful if you are replying to > a single message. Ok, thanks. Series of patches posted with `git send-email`. [PATCH v2 01/27] new Metalink functionalities: http://lists.gnu.org/archive/html/bug-wget/2016-09/msg00133.html > > > > What about the gpg signature? > > I have not tried that, but I guess git send-email should be able to keep > signed commits. At least if the patches are applied to the same commit > and the checksum is not changed. Thanks again for this tip. > > Thanks, > Giuseppe Regards, Matthew -- Matthew White <mehw.is...@inventati.org>
pgpaiRwBR5nFu.pgp
Description: PGP signature
