On Sat, Feb 27, 2021 at 12:15 AM Kevin Oberman wrote:
> Well, back to a full clone. Thanks for the "--unshallow" argument, but so
> far it has failed twice. I suspect that it's my urtwn interface is bad.
> I'll swap it out tomorrow and see it that fixes it.
>
> I am a bit surprised at how little
Well, back to a full clone. Thanks for the "--unshallow" argument, but so
far it has failed twice. I suspect that it's my urtwn interface is bad.
I'll swap it out tomorrow and see it that fixes it.
I am a bit surprised at how little more space the full clone takes. I was
really expecting it to be
On Fri, 26 Feb 2021 at 12:10, Helge Oldach wrote:
>
> A shallow tree is about 1.6G. If you want to patch source (say, from
> a SA or EN) you certainly also need space for an object tree which is
> about 4.5G. The total is >6G.
>
> I'd say relative to the total required to build, the 1.1G "savings"
On Fri, Feb 26, 2021 at 9:35 AM Ed Maste wrote:
> On Thu, 25 Feb 2021 at 15:58, Warner Losh wrote:
> >
> > The problem, though, can happen when you run a shallow clone or gitup to
> > get the sources and build from that. In that case the v number is bogus
> > (hmmm, we should omit it when we hav
On Thu, 25 Feb 2021 at 15:58, Warner Losh wrote:
>
> The problem, though, can happen when you run a shallow clone or gitup to
> get the sources and build from that. In that case the v number is bogus
> (hmmm, we should omit it when we have a shallow clone maybe).
I want to clarify one point here
Dear All,
I think I found a bug that is similar to an already reported one, but
I am not sure.
Description: when a BSD partition is mounted to / (suppose
/dev/da0s2a), if I try to mount its containing slice (/dev/da0s2) I
receive a ``strange'' error message, and from that moment the mounted
files
On 2/26/2021 10:22, Ed Maste wrote:
On Thu, 25 Feb 2021 at 16:57, Karl Denninger wrote:
The time (and present items) on a given machine to know whether it is
covered by a given advisory under the "svn view of the world" is one
command, and no sources. That is, if the advisory says "r123456" ha
On Thu, 25 Feb 2021 at 16:57, Karl Denninger wrote:
>
> The time (and present items) on a given machine to know whether it is
> covered by a given advisory under the "svn view of the world" is one
> command, and no sources. That is, if the advisory says "r123456" has
> the fix, then if I do a "un