From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] 43be8e: Renamed polipo-latest back to polipo
Date: Tue, 31 Jan 2012 15:32:58 -0800 [thread overview]
Message-ID: <4f287a2a985ec_61c93fd02c3af2f056112@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: 43be8ebde6f526e046b0262dd8444242f404d4bf
https://github.com/dtaht/ceropackages/commit/43be8ebde6f526e046b0262dd8444242f404d4bf
Author: Dave Taht <d@taht.net>
Date: 2012-01-31 (Tue, 31 Jan 2012)
Changed paths:
R net/polipo-latest/Makefile
R net/polipo-latest/files/polipo.config
R net/polipo-latest/files/polipo.init
A net/polipo/Makefile
A net/polipo/files/polipo.config
A net/polipo/files/polipo.init
Log Message:
-----------
Renamed polipo-latest back to polipo
When I'm not explicitly trying to push the bleeding edge and
maintain two versions to play with, it makes more sense to
use the openwrt feed preference function when installing
the package. This makes for minimal differences between the two
and an easy update to push out to openwrt head when it proves
stable.
reply other threads:[~2012-01-31 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f287a2a985ec_61c93fd02c3af2f056112@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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