On Fri, Jun 21, 2013, at 2:42, Aymeric Mansoux wrote:
My question therefore is: while I will mention these problems upstream,
should I also make the PR? Contact the port maintainer directly?
I understand it is not FreeBSD specific (same issue on Debian Sid)
however it really make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an Acer (S3-391) laptop, its a recent model with an SSD and HHD
for a very nice price.
I'm running FreeBSD 10-current, because of the wireless driver.
I notice I can't use the brightness hotkeys (Fn + Left/Right Arrows)
even with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/23/13 00:17, Miguel Clara wrote:
I have an Acer (S3-391) laptop, its a recent model with an SSD and
HHD for a very nice price.
I'm running FreeBSD 10-current, because of the wireless driver.
I notice I can't use the brightness hotkeys
I'm using freebsd-update to upgrade my system to the latest minor release.
At a couple points in the process, I get weird status indicators (percentages)
showing me that something is happening:
Fetching 1 metadata files... 70.5%
done.
70.5%
70.5%
74.2%
74.2%
81.7%
81.7%
70.5%
I'm using freebsd-update to upgrade my system to the latest minor version
(from 8.3-RELEASE to 8.4-RELEASE).
I'm surprised that the merge handling system isn't more robust. When upgrading
the old way, from source, I was used to using mergemaster to handle any
merges that couldn't be done
