From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Merge Request for several git branches
Date: Sat, 24 Jan 2015 23:21:52 +0100 [thread overview]
Message-ID: <1422138112.2761.13.camel@ipfire.org> (raw)
In-Reply-To: <1421940603.16214.66.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
I've put several updates and small bug fixes on my person IPFire 3.x
repository:
* grub2-fix
* dracut-update
* coreutils-update
* util-linux-update
* systemd-215
* sysvinit
Please review them and merge them into the main repository.
-Stefan
> This is in the "next" branch.
>
> The master branch has already been closed for the release of IPFire 2.17
> and only bug fixes go there.
>
> -Michael
>
> On Thu, 2015-01-22 at 16:26 +0100, ben(a)beert.de wrote:
> > Hi,
> > this is still not in the master branch.. why?
> >
> > Ben
> >
> > Am 2014-12-29 19:19, schrieb Michael Tremer:
> > > Thanks. Merged.
> > >
> > > On , Benjamin Schweikert wrote:
> > >> Hi,
> > >> I updated and tested the nginx package in my nginx git repo. Please
> > >> merge to next Core update.
> > >>
> > >> Ben
> > >> _______________________________________________
> > >> Development mailing list
> > >> Development(a)lists.ipfire.org
> > >> http://lists.ipfire.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2015-01-24 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fc70257bc00038c7eeaa148a1ede607@beert.de>
2015-01-22 15:30 ` Merge Request for nginx-1.6.2 Michael Tremer
2015-01-24 22:21 ` Stefan Schantl [this message]
2015-01-29 13:31 ` Merge Request for several git branches Michael Tremer
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=1422138112.2761.13.camel@ipfire.org \
--to=stefan.schantl@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