From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] htop: Update to 3.0.3
Date: Sun, 20 Dec 2020 10:45:25 +0100 [thread overview]
Message-ID: <6DCC3A87-820C-40F1-B70F-B2C6A735D98F@ipfire.org> (raw)
In-Reply-To: <4581e5e5-046d-61ae-8995-6c46c3cef630@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]
Hi,
Yes can do :)
-Michael
> On 18 Dec 2020, at 21:35, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>
> Hi Michael,
>
> I am sorry but I have also realised that I missed off the rootfiles with htop-3.0.3.
>
> Can you please unmerge it and I will redo that one as well and reissue it as a v2.
>
> Very sorry,
>
> Adolf.
>
> On 18/12/2020 12:16, Adolf Belka wrote:
>> Hi Nichael,
>>
>>
>> On 18/12/2020 10:53, Michael Tremer wrote:
>>> Hi,
>>>
>>>> On 17 Dec 2020, at 17:13, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>>>>
>>>> Update htop from 3.0.2 to 3.0.3
>>>> See the Change Log for details of changes
>>>> https://github[.]com/htop-dev/htop/blob/master/ChangeLog
>>>> Signed-off-by: Adolf Belka <ahb.ipfire(a)gmail.com>
>>>
>>> I would help Git and Patchwork if you leave an empty line between your commit message and the Signed-off-by: line.
>>>
>>> I use “git commit -s” which adds this automatically.
>>
>> Whoops. I also use git commit -s but then I have been filling the space up (Duuuuh).
>> Won't do it in future.
>>
>> Regards,
>> Adolf.
>>
>>>
>>> This isn’t a major issue, but sometimes I edit it and sometimes I forget when I merge the patch :)
>>>
>>> Best,
>>> -Michael
>>>
>>>> ---
>>>> lfs/htop | 6 +++---
>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/lfs/htop b/lfs/htop
>>>> index 8bf588be9..c081d6dc9 100644
>>>> --- a/lfs/htop
>>>> +++ b/lfs/htop
>>>> @@ -24,7 +24,7 @@
>>>>
>>>> include Config
>>>>
>>>> -VER = 3.0.2
>>>> +VER = 3.0.3
>>>>
>>>> THISAPP = htop-$(VER)
>>>> DL_FILE = $(THISAPP).tar.gz
>>>> @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
>>>> DIR_APP = $(DIR_SRC)/$(THISAPP)
>>>> TARGET = $(DIR_INFO)/$(THISAPP)
>>>> PROG = htop
>>>> -PAK_VER = 13
>>>> +PAK_VER = 14
>>>>
>>>> DEPS =
>>>>
>>>> @@ -46,7 +46,7 @@ objects = $(DL_FILE)
>>>>
>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>>
>>>> -$(DL_FILE)_MD5 = fb848a1c91871d134c785bccb560ca8d
>>>> +$(DL_FILE)_MD5 = b51b9b42b92c1f71656244ba3164da50
>>>>
>>>> install : $(TARGET)
>>>>
>>>> --
>>>> 2.29.2
>>>>
>>>
prev parent reply other threads:[~2020-12-20 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 16:13 Adolf Belka
2020-12-18 9:53 ` Michael Tremer
2020-12-18 11:16 ` Adolf Belka
2020-12-18 20:35 ` Adolf Belka
2020-12-20 9:45 ` Michael Tremer [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=6DCC3A87-820C-40F1-B70F-B2C6A735D98F@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