On 24/12/20 11:15, Michael Grimm wrote:
Correction:
On 24. Dec 2020, at 15:11, Michael Grimm wrote:
In the past I could easily judge if there was a need to buildworld or
buildkernel: If uname shows a larger revision number than those in advisories
or notices.
In the past I could easily ju
On Mon, 28 Dec 2020 at 07:08, Renato Botelho wrote:
>
> FreeBSD bast.garga.net.br 13.0-CURRENT FreeBSD 13.0-CURRENT #19
> 3cc0c0d66a0-c255241(main)-dirty:
> ^
> This is an incremental counter of commits
Also, uqs@ recently fixed an issue in newvers.sh (including the fina
I got this panic again today in a VM when quitting a gdb
session after killing a child process via 'kill'.
panic: Assertion pgrp->pg_jobc > 0 failed at /git/bhyve/sys/kern/kern_proc.c:816
cpuid = 1
time = 1609185862
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
On 12/28/20 12:24 PM, John Baldwin wrote:
> I got this panic again today in a VM when quitting a gdb
> session after killing a child process via 'kill'.
>
> panic: Assertion pgrp->pg_jobc > 0 failed at
> /git/bhyve/sys/kern/kern_proc.c:816
> cpuid = 1
> time = 1609185862
> KDB: stack backtrace:
>
what would be the git command for reverting source to a previous version
using these numbers? for example, with svn and old numbers:
svnlite update -r367627 /usr/src
this is needed often when it blows up for someone tracking current
On 12/28/20 11:27 AM, Ed Maste wrote:
On Mon, 28 Dec 2020 at
On 12/28/20 4:38 PM, monochrome wrote:
what would be the git command for reverting source to a previous
version using these numbers? for example, with svn and old numbers:
svnlite update -r367627 /usr/src
I will generally just checkout the short git hash like so in my local
checkout:
$ git
monochrome wrote this message on Mon, Dec 28, 2020 at 19:38 -0500:
> what would be the git command for reverting source to a previous version
> using these numbers? for example, with svn and old numbers:
> svnlite update -r367627 /usr/src
>
> this is needed often when it blows up for someone trac
Kurt Jaeger wrote this message on Wed, Dec 23, 2020 at 13:15 +0100:
> Hi!
>
> > It's also hard to collect ALL the keys of the devs at any point in
> > time to decide if that key is authorized to sign a commit in the
> > repo...
>
> We do have most of the keys in docs/share/pgpkeys/ plus history.
On Mon, Dec 28, 2020 at 04:56:39PM -0800, John-Mark Gurney wrote:
> monochrome wrote this message on Mon, Dec 28, 2020 at 19:38 -0500:
> > what would be the git command for reverting source to a previous version
> > using these numbers? for example, with svn and old numbers:
> > svnlite update -r3
Steffen Nurpmeso wrote this message on Wed, Dec 23, 2020 at 17:24 +0100:
> |Then there's also the point that the repo is (looks like it) using
> |SHA-1 hashes, which are effectively broken, so depending upon them
> |to validate the tree is questionable anyways.
>
> git uses the hardened SHA-1 f
On Mon, Dec 28, 2020, 6:19 PM John-Mark Gurney wrote:
> Steffen Nurpmeso wrote this message on Wed, Dec 23, 2020 at 17:24 +0100:
> > |Then there's also the point that the repo is (looks like it) using
> > |SHA-1 hashes, which are effectively broken, so depending upon them
> > |to validate the
this didn't seem to work, and now git is saying: You are not currently
on a branch.
since the incremental numbers aren't in the git log does it make more
sense to use the short hash like this? other different responses were
focused on the incremental commit number.
Also, I saw someone mention th
sry forgot details:
source tree @ ead01bfe8
git -C /usr/src checkout gf20c0e331
error: pathspec 'gf20c0e331' did not match any file(s) known to git
what is the 'g' for?
git -C /usr/src checkout f20c0e331
M sys/amd64/conf/GENERIC
HEAD is now at f20c0e331 caroot: drop $FreeBSD$ expansion f
13 matches
Mail list logo
