Thanks, Olivier, for the quick response. Now I don't have to do a system
build!
Neither command is what I'd call 'intuitive', so it would have taken me a
long time to find either of them. I cut and pasted the 'git branch' command
and it took me a moment to realize what that meant. Never ran "grep -l" on
a pipe, I guess.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Wed, Feb 24, 2021 at 10:06 AM Olivier Certner <olivier.free...@free.fr>
wrote:
> Hi,
>
> In your base git repository, type:
> git rev-list <uname_hash> | grep -lF <searched_hash>
>
> This outputs something ("(standard input)") iff you have it in.
>
> In order to limit the search time in case of a false result, you'd better
> pass
> the --since=<oldest_date> to git rev-list.
>
> There is an alternative if you have a branch pointing to your uname hash:
> git branch --contains <searched_hash> | grep -lF <your_branch>
>
> Regards.
>
> --
> Olivier Certner
>
>
>
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
