From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Merger request - ddns / gub2 / plymouth
Date: Wed, 10 Dec 2014 14:26:42 +0100 [thread overview]
Message-ID: <1418218002.14452.114.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1418194850.12326.6.camel@acer.stevee>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Hi,
thanks for sendning this in.
On Wed, 2014-12-10 at 08:00 +0100, Stefan Schantl wrote:
> Dear list followers,
>
> I've prepared and stored some commits / branches in my personal IPFire
> 3.x git repository which i want to request to merge into the main tree.
>
> DDNS - Adjoin and update to latest version.
> http://git.ipfire.org/?p=people/stevee/ipfire-3.x.git;a=shortlog;h=refs/heads/ddns
I merged this, but squashed both commits into one. The reason for that
is that the first commit wouldn't build correctly as there was no
source_dl set.
We should also add some systemd timer events that take care of ddns
being started at the right time to update the hostnames.
I opened a bug report and assigned it to you:
https://bugzilla.ipfire.org/show_bug.cgi?id=10698
> grub2: A fix to get the "grub-mkconfig" command working again.
> http://git.ipfire.org/?p=people/stevee/ipfire-3.x.git;a=shortlog;h=refs/heads/grub2-fix
We should try to get rid of those workarounds eventually, but I merged
it for now.
> Plymouth: Update to 0.9.0.
> http://git.ipfire.org/?p=people/stevee/ipfire-3.x.git;a=shortlog;h=refs/heads/plymouth-update
Merged as well.
> Thanks in advance,
>
> -Stefan
>
-Michael
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-10 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 7:00 Stefan Schantl
2014-12-10 13:26 ` 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=1418218002.14452.114.camel@rice-oxley.tremer.info \
--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