From owner-freebsd-arch@freebsd.org Wed Jan 27 19:20:43 2021 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 003A74E6AE4 for ; Wed, 27 Jan 2021 19:20:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQtjk0gj3z3F5L for ; Wed, 27 Jan 2021 19:20:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72b.google.com with SMTP id 19so2902334qkh.3 for ; Wed, 27 Jan 2021 11:20:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KYtZb+x2IA4Wg2HJlmyUQWGa7ACFB0R/ol7oMyscYUs=; b=sZOwzdEApRp4QJ+50+aiijVNXh82GS9SiexDUDVerXMLJJlLTA9YMCFuH2DZDvAFOq sRt5VB68JlaapjbGxmZIV1GGKq/xWD1gNNekINUeIwMR4S4LOJtuco+JojoJeP+zqNqv bFfxS6eCmL+oNOsoJvs/YHpn3dyqDewssiPpNL5q++rT3s7//+Ti7xDhxkSfERFtJuq3 6z8b4jQFFxYa56QXcrLePKPXE4fFxj5duRntsEXURrAEi1mXEOsbqxraKR61MnW/JGbD Hw/JAU5LHZ/D0LH4M/bIKdF3XBkn3EFtlIBxkntqvWjiDMCrbsUt3deBzB+w1jO51Tyz TQew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KYtZb+x2IA4Wg2HJlmyUQWGa7ACFB0R/ol7oMyscYUs=; b=bPs0U83A0oS4/YEfxi3hxrinRAoHtq9uV+eoknBXTU+FGGnAYdO3EcTcsW6q0AgnYd VKCG3MnzZDRrzMEqx3sFMUBRi3shRQ1emXoRjDqYntoCJdMK73Emf1eTjmPJC2In1dOq j95y7HgfPkjPfm1i6CAXnoE/kcxwfgOd2YvhvEJ/U1nfVPS5M0/UnF2WCFAhekY/CPoQ ra4OUiTOq+QttXTd3FIqCCBUrpzDHEJUOMvnvCD+Q3aMhqMiNkedwiNqxNP6wCLFqM13 bJnNuBYh8lnP+4ze2ZaL7zwP6K+OKLSmpMIP18FxJRU9EFj9gm/7AjFVWBizROS1o1hn bg0w== X-Gm-Message-State: AOAM533EI8nl218LwcN0ckAfQJH65MgrctfYEoBDYnicdaxGSg4LJTet D1RnXHQhICiWNtL22jONkr+EtHDuPRI7X4Ho+Wnnw1DN9Ka7Og== X-Google-Smtp-Source: ABdhPJyDPfScYKUdGV+vVv1+EULa77oHMbQ+8mDteDBe7MZdue/qc0eX/gt3qRbMrZEBH1GdIawJ/cnMxNFr0ZFQRPY= X-Received: by 2002:a05:620a:9cf:: with SMTP id y15mr12307315qky.44.1611775241062; Wed, 27 Jan 2021 11:20:41 -0800 (PST) MIME-Version: 1.0 References: <10fec1da415cd8d3c080a2173b9245ff35fceac8.camel@freebsd.org> In-Reply-To: From: Warner Losh Date: Wed, 27 Jan 2021 12:20:30 -0700 Message-ID: Subject: Re: Change in the uname To: Li-Wen Hsu Cc: Ian Lepore , "freebsd-arch@freebsd.org" X-Rspamd-Queue-Id: 4DQtjk0gj3z3F5L X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=sZOwzdEA; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::72b) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::72b:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72b:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::72b:from]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-arch] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 19:20:43 -0000 On Mon, Jan 25, 2021 at 3:03 PM Li-Wen Hsu wrote: > On Tue, Jan 26, 2021 at 5:04 AM Ian Lepore wrote: > > That all sounds good, except the 'v' is a bit odd, normally it implies > > a "version" number, which isn't exactly what this is. How about 'n' or > > '#' since it's just a count? > > Seconded, sorry for discussing the color of bikeshed, but 'v' is also > not intuitive to me. Since it is still a counter, and we are removing > the 'g' in the second part, cXXXXX-HASH is still distinguishable with > the old cXXXXX-gHASH. > > Or, maybe call it gXXXXX-HASH which stands for git commit count XXXXX, > with hash value HASH? > I can do 'n' instead of 'v'. I think that 'g' would be a bit confusing since the connection to git is less obvious. I happen to like the 'old school' versioning that would do X.Y(Z) where Z is a count of changes (whatever that means) (either since X.0 started or back to the start of the thing). That would be branch(version)-hash. I opted to not implement that, though. While I like it, I know I'm old school and this style has fallen out of fashion since the 80s and 90s when it was popular on the 'big iron' (TOPS-20, IBM, etc) as the 'big iron' culture has given way to other schools of thought. It's also harder to script parse and harder to implement. All in all, I think 'v' or 'n' is best and most clear. # I'd like to avoid because in the non-reproducible build case #x is the build number. Any last comments before I roll this in later today to hit the MFC window? Warner