Date: Mon, 25 Jan 2021 04:15:24 +0900 (JST) From: Yasuhiro Kimura <yasu@utahime.org> To: sjg@juniper.net Cc: sgk@troutmask.apl.washington.edu, freebsd-current@freebsd.org Subject: Re: Getting /usr/src to match specific git hash? Message-ID: <20210125.041524.2140874210852374119.yasu@utahime.org> In-Reply-To: <18487.1611511538@kaos.jnpr.net> References: <20210124035852.GA73653@troutmask.apl.washington.edu> <18487.1611511538@kaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Simon J. Gerraty" <sjg@juniper.net> 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 sources". There was bug in sys/conf/newvers.sh that reports the result of dirtyness check in reverse. It was introduced at commit 029ca1842fa on 2002/12/17 and fixed at commit 17eba5e32a2 on 2020/12/23. And commit 3cc0c0d66a0 is between them. So in this case "3cc0c0d66a0-c255241(main)-dirty" means there isn't any change in src tree. Just FYI. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210125.041524.2140874210852374119.yasu>