On 2021-Jan-24, at 23:37, Mark Millard wrote:
>
>> How cat one track multiple branches with git without keeping entirely
>> separate trees?
>
> There are multiple possibilities here and it is not
> clear which you are hoping for.
>
> A) You could be trying to avoid having two separate .git
> How cat one track multiple branches with git without keeping entirely
> separate trees?
There are multiple possibilities here and it is not
clear which you are hoping for.
A) You could be trying to avoid having two separate .git
copies around, each also with checked-out material.
(2
On 2021-01-24 21:35:40 (+0800), mj-mailingl...@gmx.de wrote:
- some FreeBSD project related files, like:
bsd-family-tree.dot, committers-*.dot, organization.dot
These would better be part of the documentation.
BTW, on 12.x they are out of date:
> (4) processes being killed with out-of-swapspace messages
> even though I have 4 GB of untouched swap space. Might
> be associated with (3).
[This is mostly a FYI in case the material is unfamiliar.]
Only believe the detailed wording of messages of the form:
"was killed: out of swap
On Sat, Jan 23, 2021 at 03:25:59PM +, Rick Macklem wrote:
> Ronald Klop wrote:
> >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote:
> >But I think for Tor to support KTLS it needs to implement some things
> >itself. More information about that could be asked at the maintainer of
> >the
From: Mark Linimon
Subject: Re: pkg for 14-current
Date: Mon, 25 Jan 2021 03:41:26 +
> On Sun, Jan 24, 2021 at 07:45:08PM +0900, Yasuhiro Kimura wrote:
>> By the way, when -CURRENT was bumped from 12 to 13, there were some
>> ports that failed to be built on 13-CURRENT simply because they
On 2021-01-25 10:57:19 (+0800), Thomas Mueller wrote:
It is in the mini primer I wrote, along with how to bisect and other
useful
things. This will migrate into the handbook once the doc tree
converts to
asciidoc (happening this weekend).
On Sun, Jan 24, 2021 at 07:45:08PM +0900, Yasuhiro Kimura wrote:
> By the way, when -CURRENT was bumped from 12 to 13, there were some
> ports that failed to be built on 13-CURRENT simply because they don't
> expect there is version 13.x of FreeBSD. And probably such ports fails
> to be built on
> It is in the mini primer I wrote, along with how to bisect and other useful
> things. This will migrate into the handbook once the doc tree converts to
> asciidoc (happening this weekend).
> https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md
> Warner
I looked at your
On Sun, Jan 24, 2021 at 3:40 PM Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Sun, Jan 24, 2021 at 03:22:18PM -0700, Warner Losh wrote:
> > On Sun, Jan 24, 2021, 12:14 PM Steve Kargl <
> s...@troutmask.apl.washington.edu>
> > wrote:
> >
> >>
> >> Any advice on how to jump, say, 4
after looking in the git log for the hash I use:
git -C /usr/src reset --hard
you will lose any local changes
On 1/24/21 5:40 PM, Steve Kargl wrote:
On Sun, Jan 24, 2021 at 03:22:18PM -0700, Warner Losh wrote:
On Sun, Jan 24, 2021, 12:14 PM Steve Kargl
wrote:
Any advice on how to jump,
Hello:
On a system now running:
14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: Sun Jan 24
14:16:54 EST 2021 amd64
(src+ports updated at midnight US EST)
with PORTS_MODULES="drm-current-kmod gpu-firmware-kmod", starting
the system _without_ loading drm results in
On Sun, Jan 24, 2021 at 03:22:18PM -0700, Warner Losh wrote:
> On Sun, Jan 24, 2021, 12:14 PM Steve Kargl
> wrote:
>
>>
>> Any advice on how to jump, say, 4 days ahead of the current
>> date of the src/ tree? That is, I have src/ that should
>> correspond to 24 Dec 2020. How do I jump to 28
On Sun, Jan 24, 2021 at 3:22 PM Warner Losh wrote:
>
>
> On Sun, Jan 24, 2021, 12:14 PM Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
>> On Sun, Jan 24, 2021 at 09:00:45AM -0700, Warner Losh wrote:
>> > On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet <
>> jbt...@iherebuywisely.com>
On Sun, Jan 24, 2021, 12:14 PM Steve Kargl
wrote:
> On Sun, Jan 24, 2021 at 09:00:45AM -0700, Warner Losh wrote:
> > On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet >
> > wrote:
> >
> > >
> > >
> > > On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl <
> > > s...@troutmask.apl.washington.edu> wrote:
Steve Kargl wrote:
> Suppose further that one had to re-install a 32-bit
> i386-*-freebsd with the 24 Dec 2020 image available
> from freebsd.org.
>
> uname -a for the booted kernel shows
>
> % uname -a
> FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
> 3cc0c0d66a0-c255241(main)-dirty:
On Sun, Jan 24, 2021 at 11:14:45AM -0800, Steve Kargl wrote:
> ...
> Any advice on how to jump, say, 4 days ahead of the current
> date of the src/ tree? That is, I have src/ that should
> correspond to 24 Dec 2020. How do I jump to 28 Dec 2020?
I (happen to) track FreeBSD head, stable/12 (and
From: "Simon J. Gerraty"
Subject: Re: Getting /usr/src to match specific git hash?
Date: Sun, 24 Jan 2021 10:05:38 -0800
> As others have described, you can clone and 'git checkout 3cc0c0d66a0'
> but that "-dirty" above implies the tree had changes, so you cannot
> reproduce "the exact
On Sun, Jan 24, 2021 at 09:00:45AM -0700, Warner Losh wrote:
> On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet
> wrote:
>
> >
> >
> > On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura
OK, building ports against a clean installation of 13.0-ALPHA2 has no problem
with ncurses.
But devel/glib20 fails for no obvious reason closer to the end of building
process... I just wonder: do I need to report this to port maintainers or wait
till it settles up somehow? A good deal of
On Sun, Jan 24, 2021, 9:05 AM Shawn Webb wrote:
> On Sun, Jan 24, 2021 at 09:00:45AM -0700, Warner Losh wrote:
> > On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet >
> > wrote:
> >
> > >
> > >
> > > On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl <
> > > s...@troutmask.apl.washington.edu> wrote:
>
On Sun, Jan 24, 2021 at 02:53:41PM +, Kostya Berger wrote:
> OK, building ports against a clean installation of 13.0-ALPHA2 has no problem
> with ncurses.
> But devel/glib20 fails for no obvious reason closer to the end of building
> process... I just wonder: do I need to report this to
On Sun, Jan 24, 2021 at 09:00:45AM -0700, Warner Losh wrote:
> On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet
> wrote:
>
> >
> >
> > On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura
On Sun, Jan 24, 2021, 6:05 AM Jeffrey Bouquet
wrote:
>
>
> On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote:
> > > From: Steve Kargl
> > > Subject: Getting /usr/src to match
> On Jan 24, 2021, at 05:36, mj-mailingl...@gmx.de wrote:
> What is the history behind /usr/share/misc?
Hi Martin,
Have you read “man hier”, by chance? This might elucidate things a bit.
Cheers,
-Enji
___
freebsd-current@freebsd.org mailing list
While browsing the filesystem, i found the folder /usr/share/misc and now i am
curious, what kind of files and why they were put there.
The list on "13.0-ALPHA2 stable/13-f76393a63" looks like this:
-r--r--r-- 1 root wheel 3170 Jan 24 09:18 ascii
-r--r--r-- 1 root wheel 5265 Jun 25
On Sat, 23 Jan 2021 20:14:03 -0800, Steve Kargl
wrote:
> On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote:
> > From: Steve Kargl
> > Subject: Getting /usr/src to match specific git hash?
> > Date: Sat, 23 Jan 2021 19:58:52 -0800
> >
> > > Suppose one has an empty /usr/src.
>
Yasuhiro Kimura writes:
G> From: Masachika ISHIZUKA
> Subject: pkg for 14-current
> Date: Sun, 24 Jan 2021 19:11:28 +0900 (JST)
>
>> Hi.
>>
>> I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg.
>> I cannot get meta files for 14-current.
>> How can I use pkg on
On Sun, Jan 24, 2021 at 06:11:04AM -0600, donaldwillin...@gmail.com wrote:
> I'm happy the number was changed. To many, the number "13" is
> considered to be bad luck.
>
It was not "changed" for that reason.
It's a natural progression from 11 to 12 to 13 to 14 (to 15 ...).
It's the way
I'm happy the number was changed. To many, the number "13" is
considered to be bad luck.
On Sat, 2021-01-23 at 17:51 -0800, David Wolfskill wrote:
> On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote:
> > ...
> > > That is correct, 13-stable has been branched from 13-current
> >
Hi,
On 25/11/20 1:12 pm, Alexander V. Chernikov wrote:
21.11.2020, 22:48, "Guy Yur" :
Hi,
When adding a route with a netmask, add_route() in route_ctl.c
adds the route with destination address masked.
If the add failed (for example, the route exists) it calls
lookup_prefix() with the original
From: Yasuhiro Kimura
Subject: Re: pkg for 14-current
Date: Sun, 24 Jan 2021 19:18:29 +0900 (JST)
>> I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg.
>> I cannot get meta files for 14-current.
>> How can I use pkg on 14-current ?
>>
> All what you can do is to
From: Masachika ISHIZUKA
Subject: pkg for 14-current
Date: Sun, 24 Jan 2021 19:11:28 +0900 (JST)
> Hi.
>
> I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg.
> I cannot get meta files for 14-current.
> How can I use pkg on 14-current ?
>
>> # pkg update
>>
Hi.
I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg.
I cannot get meta files for 14-current.
How can I use pkg on 14-current ?
> # pkg update
> Updating FreeBSD repository catalogue...
> pkg: http://pkgmir.geo.freebsd.org/FreeBSD:14:amd64/latest/meta.txz: Not
On 2021-Jan-22, at 01:45, Mark Millard wrote:
> Given an already built, installed and booted system version, I've
> noted a big difference for META_MODE in 2 rebuild contexts (no
> source updates involved):
>
> *) Prior buildworld buildkernel, installkernel, installworld, boot
> presumed
35 matches
Mail list logo
