From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Question regarding commit fd2dccaabb2e28cf875d7d81c7faf90f7941f56b
Date: Wed, 01 Jan 2020 20:18:00 +0000 [thread overview]
Message-ID: <3be68b16-54ef-1fa6-e370-fdf4f072651c@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hello Arne, hello list (CC'ed),
I just noticed commit fd2dccaabb2e28cf875d7d81c7faf90f7941f56b was merged
into the "master" branch of https://git.ipfire.org/?p=ipfire-2.x.git;a=summary ,
but does not seem to be applied to the "next" branch, too.
Is this intentional? If yes, why?
Anyway:
> #define YEAR 2020
> #include <bestwishes>
> #include <peace>
> #include <security>
:-)
Thanks, and best regards,
Peter Müller
next reply other threads:[~2020-01-01 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 20:18 Peter Müller [this message]
2020-01-02 16:01 ` Arne Fitzenreiter
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=3be68b16-54ef-1fa6-e370-fdf4f072651c@ipfire.org \
--to=peter.mueller@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