From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ddns: Update to 012
Date: Tue, 05 Nov 2019 15:51:13 +0000 [thread overview]
Message-ID: <C7ABBCB6-AC39-4F5F-9D54-054B600F2112@ipfire.org> (raw)
In-Reply-To: <50a0b7092c4dbc0deb5186c3bbdd14552b0b7615.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
> On 5 Nov 2019, at 12:16, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> Hello Michael,
>
> the DDNS git is correct like it actually is. Every single patch which
> was located on the ddns Mailing list has been merged.
Indeed.
>
> What are that "urgent bug fixes" which you asked about?
https://bugzilla.ipfire.org/show_bug.cgi?id=12195
https://bugzilla.ipfire.org/show_bug.cgi?id=11561
These are easy. Please tell reporters that they should send potential fixes to the mailing lists.
Best,
-Michael
>
> Best regards,
>
> -Stefan
>> Hi Stefan,
>>
>> Yes, finally.
>>
>> However, I cannot find all of those commits for this release in the
>> master branch.
>>
>> Could you check and potentially push again? I just think you didn’t
>> push master.
>>
>> https://git.ipfire.org/?p=ddns.git;a=summary
>>
>> This one just shows a slightly typo-ed tag:
>>
>>
>> https://git.ipfire.org/?p=ddns.git;a=shortlog;h=ca9c381a5388ff10243048903f11192b95518c72
>>
>> Are none of the urgent bug fixes in this release?
>>
>> -Michael
>>
>>> On 5 Nov 2019, at 09:37, Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> wrote:
>>>
>>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> ---
>>> lfs/ddns | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/lfs/ddns b/lfs/ddns
>>> index cd56ee72b..a6ca2e35d 100644
>>> --- a/lfs/ddns
>>> +++ b/lfs/ddns
>>> @@ -24,7 +24,7 @@
>>>
>>> include Config
>>>
>>> -VER = 011
>>> +VER = 012
>>>
>>> THISAPP = ddns-$(VER)
>>> DL_FILE = $(THISAPP).tar.xz
>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>>
>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>
>>> -$(DL_FILE)_MD5 = f0399ba5bad3272f32e539c45cd1abe9
>>> +$(DL_FILE)_MD5 = 00e70e8bf619148e14b6f6836314bbb7
>>>
>>> install : $(TARGET)
>>>
>>> --
>>> 2.20.1
>>>
>
next prev parent reply other threads:[~2019-11-05 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:37 Stefan Schantl
2019-11-05 10:18 ` Michael Tremer
2019-11-05 12:16 ` Stefan Schantl
2019-11-05 15:51 ` Michael Tremer [this message]
2019-11-05 18:23 ` [PATCH] ddns: Import upstream patch for NoIP.com Stefan Schantl
2019-11-06 15:36 ` Michael Tremer
2019-11-12 8:09 ` [PATCH] ddns: Import rename NoIP.com handle back to no-ip.com patch Stefan Schantl
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=C7ABBCB6-AC39-4F5F-9D54-054B600F2112@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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