On Wed, Nov 20, 2019 at 02:52:22PM -0800, Mark Millard wrote:
>
> Unfortunately for Bob P., no suggestion can meet his full criteria. So
> he has several suggestions to potentially pick from or to use in
> combination.
>
This is a most gracious way of saying my expectations are
unreasonable. Sad
On 11/20/19 12:02 PM, bob prohaska wrote:
On Wed, Nov 20, 2019 at 11:18:41AM -0700, Warner Losh wrote:
On Wed, Nov 20, 2019 at 10:39 AM bob prohaska wrote:
From time to time it would be handy to revert freebsd-current to
an older, well-behaved revision.
Is there a mechanism for identifying
On 2019-Nov-20, at 14:28, Julian Elischer wrote:
> On 11/20/19 1:51 PM, Mark Millard wrote:
>> Bob P. wrote for an aarch64 context:
>>
>>> From time to time it would be handy to revert freebsd-current to
>>> an older, well-behaved revision.
>>>
>>> Is there a mechanism for identifying revisi
On 11/20/19 1:51 PM, Mark Millard wrote:
Bob P. wrote for an aarch64 context:
From time to time it would be handy to revert freebsd-current to
an older, well-behaved revision.
Is there a mechanism for identifying revision numbers that
will at least compile and boot, by date?
In my case build
Bob P. wrote for an aarch64 context:
> From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
> In my case buildworld seems to be markedly sl
On Wed, Nov 20, 2019 at 11:18:41AM -0700, Warner Losh wrote:
> On Wed, Nov 20, 2019 at 10:39 AM bob prohaska wrote:
>
> > From time to time it would be handy to revert freebsd-current to
> > an older, well-behaved revision.
> >
> > Is there a mechanism for identifying revision numbers that
> > wi
On Wed, Nov 20, 2019 at 10:39 AM bob prohaska wrote:
> From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
Almost all of them will compile.
On Wed, 2019-11-20 at 09:38 -0800, bob prohaska wrote:
> From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
> In my case buildworld seems
On Wed, Nov 20, 2019 at 09:38:53AM -0800, bob prohaska wrote:
> >From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
> In my case buildworl
On Thu, Nov 21, 2019 at 1:39 AM bob prohaska wrote:
>
> From time to time it would be handy to revert freebsd-current to
> an older, well-behaved revision.
>
> Is there a mechanism for identifying revision numbers that
> will at least compile and boot, by date?
>
> In my case buildworld seems to b
>From time to time it would be handy to revert freebsd-current to
an older, well-behaved revision.
Is there a mechanism for identifying revision numbers that
will at least compile and boot, by date?
In my case buildworld seems to be markedly slower than, say,
six months ago. Maybe it's hardware
11 matches
Mail list logo
