On Thu, Mar 30, 2017 at 06:44:37AM +, Miod Vallat wrote:
> >> > Ambiguous: choose package for emacs--no_x11
> >> > a 0:
> >> > 1: emacs-21.4p37-no_x11
> >> > 2: emacs-25.1p3-no_x11
> >> > Your choice:
> >>
> >> Time to choose another package?
> >
> > I think in this cas
>> > Ambiguous: choose package for emacs--no_x11
>> > a 0:
>> > 1: emacs-21.4p37-no_x11
>> > 2: emacs-25.1p3-no_x11
>> > Your choice:
>>
>> Time to choose another package?
>
> I think in this case choice is good.
Indeed, but why aren't vim-no_x11 packages listed as possible
On Wed, Mar 29, 2017 at 10:52:23PM +0200, Antoine Jacoutot wrote:
> On Wed, Mar 29, 2017 at 09:40:32PM +0200, Christian Weisgerber wrote:
> > Antoine Jacoutot:
> >
> > > Why not just:
> > >
> > > # pkg_add -v rsync chromium emacs--no_x11
> > >
> > > So we don't have to change it each release?
>
On Thu, Mar 30, 2017 at 12:47:35AM +0200, Mark Kettenis wrote:
> Looking at the code, it is possible for the device to return a packet
> that is larger than what fits into a standard 2k mbuf cluster. So
> let's replace the handrolled mbuf allocation./copy code with an
> invocation of m_devget(9),
I noticed this a few months ago, but forgot to send it.
Index: faq6.html
===
RCS file: /cvs/www/faq/faq6.html,v
retrieving revision 1.435
diff -u -p -u -r1.435 faq6.html
--- faq6.html 25 Mar 2017 19:07:05 - 1.435
+++ faq6
On Tue, Mar 28, 2017 at 02:12:42PM -0500, Job Snijders wrote:
> Dear all,
>
> BGP Origin Validation State communities are non-transitive opaque
> extended communities to carry the origination Autonomous System
> validation state inside an autonomous system. IBGP speakers that
> receive this valida
Looking at the code, it is possible for the device to return a packet
that is larger than what fits into a standard 2k mbuf cluster. So
let's replace the handrolled mbuf allocation./copy code with an
invocation of m_devget(9), which will make sure a chain is allocated
for large packets.
Lightly t
On Wed, Mar 29, 2017 at 09:40:32PM +0200, Christian Weisgerber wrote:
> Antoine Jacoutot:
>
> > Why not just:
> >
> > # pkg_add -v rsync chromium emacs--no_x11
> >
> > So we don't have to change it each release?
>
> Because people won't let Emacs 21 die.
Ah but, you just killed me :-)
> Ambig
Antoine Jacoutot:
> Why not just:
>
> # pkg_add -v rsync chromium emacs--no_x11
>
> So we don't have to change it each release?
Because people won't let Emacs 21 die.
Ambiguous: choose package for emacs--no_x11
a 0:
1: emacs-21.4p37-no_x11
2: emacs-25.1p3-no_x11
Your cho
On Wed, Mar 29, 2017 at 09:10:49PM +0200, Christian Weisgerber wrote:
> Sync the version of the example package. ok?
Why not just:
# pkg_add -v rsync chromium emacs--no_x11
So we don't have to change it each release?
> Index: root.mail
> ===
Sync the version of the example package. ok?
Index: root.mail
===
RCS file: /cvs/src/etc/root/root.mail,v
retrieving revision 1.121
diff -u -p -r1.121 root.mail
--- root.mail 5 Mar 2017 15:08:03 - 1.121
+++ root.mail 29
On Tue, Mar 07, 2017 at 10:17:16AM +0100, Patrick Wildt wrote:
> currently the pf status struct contains the time since pf was enabled as
> seen on the wall clock. This means when time drifts, or is set to some
> earlier value, the time will be off. If we use time since uptime it
> always increme
12 matches
Mail list logo