From: Sauron99@gmx.de
To: ddns@lists.ipfire.org
Subject: Aw: Re: [PULL] to add new DynDNS provider
Date: Mon, 26 Sep 2016 15:48:04 +0200 [thread overview]
Message-ID: <trinity-6594ece3-268f-44ba-9160-fcb1ebe3c03b-1474897684428@3capp-gmx-bs47> (raw)
In-Reply-To: <1474632715.7591.6.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
Hello,
sorry i have added my name to the commit as it should i think.
Sadly i don´t know how i can merge these two commits into one. I tried but i failed, it´s about this commit that should work:
https://github.com/ipfire/ddns/commit/cf3ebbce18019df41e409acc2c2f917c39cfc9c9
I hope that i fulfill you requirements so that it can be added for the next release.
Best wishes
> Gesendet: Freitag, 23. September 2016 um 14:11 Uhr
> Von: "Stefan Schantl" <stefan.schantl(a)ipfire.org>
> An: ddns(a)lists.ipfire.org
> Betreff: Re: [PULL] to add new DynDNS provider
>
> Hello,
>
> thanks for your hard work and sharing your changes with us.
>
> Unfortunately there are a few points which need to be done until we can
> merge the changes into master.
>
> * Relating to our contribution guidelines, we only accept patches with
> the full and real name (no pseudonyms).
>
> * Please merge your two commits into a single one.
>
> * Send the final patch to this mailing list.
>
> A short snipped from the README file:
>
> Please only send patches to the official mailing list:
> ddns(a)lists.ipfire.org
>
> Use the standard Git patch format as described here
> http://wiki.ipfire.org/devel/git/commit-messages
>
> and follow the general IPFire contribution guidelines
> http://wiki.ipfire.org/devel/submit-patches
>
> Please refrain from sending patches on GitHub or any other
> platforms where this repository is mirrored.
>
> Thanks in advance,
>
> -Stefan
>
> > Hello list,
> >
> > Please pull from
> >
> > https://github.com/Alternativend/ddns.git
> >
> > to get these changes: I have added Schokokeks.org to the
> > providers.py.
> >
> >
> > I hope that i have done everything right now to get this committed.
> >
> > Thanks!
> > _______________________________________________
> > ddns mailing list
> > ddns(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/ddns_______________________________________________
> ddns mailing list
> ddns(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/ddns
>
prev parent reply other threads:[~2016-09-26 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 11:43 Sauron99
2016-09-23 12:11 ` Stefan Schantl
2016-09-26 13:48 ` Sauron99 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-6594ece3-268f-44ba-9160-fcb1ebe3c03b-1474897684428@3capp-gmx-bs47 \
--to=sauron99@gmx.de \
--cc=ddns@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox