From owner-freebsd-git@freebsd.org Mon Jun 24 23:22:00 2019 Return-Path: Delivered-To: freebsd-git@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D99D215DBDB0 for ; Mon, 24 Jun 2019 23:21:59 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f68.google.com (mail-io1-f68.google.com [209.85.166.68]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 6E60C8D1DC for ; Mon, 24 Jun 2019 23:21:58 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f68.google.com with SMTP id m24so2123242ioo.2 for ; Mon, 24 Jun 2019 16:21:58 -0700 (PDT) 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=oKz629NfsrpBZUXVFGsrZ1XHvoQesE616FDxxywSnrA=; b=s+Cf2t2thDyjFMZq7qJnN45KxdD5srKypIG7E4W8XlFjpb/w/fpx+Cl3sQMfOLGLCw lYbK4f8kQlnb3wb+5mfJ2FMINDIlz3H9bCkCCnwpN/Dxh9KePPXwSm5arD6Fe6lcqK0s A/neFaCxQYAyAuhQtD8rWe+w6tM1YWP6x4oRfaKshC20n0pnUI1jeQoUwU6al6uuTEDo giF3Ji8Ik4uLoa1YAWpFyuf/RHCXKZ+OhUAaYzwORO7KhiY/rILZldYqQ7JkyYZdCSh6 /mtWxH42AwnJk/3tftoXBR5z4PSbIdwHzWBHKfhqb0ZwH0eeF8a74ibxb/nmcABrzJ9P 7/rg== X-Gm-Message-State: APjAAAWJjtfNbO3q3OYLwsGehxiwh5GDyUQh2gVXKnnhG42szfJhq6sT 32OmPjsusYKTseriZkT0CyrOiiok47OMd5A7YxI= X-Google-Smtp-Source: APXvYqwFehrGc/dLQGGgowwoEwf/waCv/ccmrAsIect9uXN75weP/4N80VlJXnjHI0ohmczCYqJyWqTzgGSU3PyGWeQ= X-Received: by 2002:a02:aa0d:: with SMTP id r13mr27383475jam.129.1561418516633; Mon, 24 Jun 2019 16:21:56 -0700 (PDT) MIME-Version: 1.0 References: <20190624205724.4c27vdvgwrlfz3uu@mutt-hbsd> In-Reply-To: <20190624205724.4c27vdvgwrlfz3uu@mutt-hbsd> From: Ed Maste Date: Mon, 24 Jun 2019 19:21:41 -0400 Message-ID: Subject: Re: Speeding up slower Git operations To: Shawn Webb Cc: freebsd-git@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 6E60C8D1DC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.68 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-git@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.86)[-0.855,0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[68.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; IP_SCORE(-1.83)[ip: (-3.33), ipnet: 209.85.128.0/17(-3.44), asn: 15169(-2.33), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jun 2019 23:22:00 -0000 On Mon, 24 Jun 2019 at 16:57, Shawn Webb wrote: > > On Mon, Jun 24, 2019 at 12:46:41PM -0400, Ed Maste wrote: > > > > This idea is implemented in review D20462, > > https://reviews.freebsd.org/D20462 > > > > Here's an example from a test machine of mine: > > # uname -a > > FreeBSD test 13.0-CURRENT FreeBSD 13.0-CURRENT > > 322839cffdb-c260903(wipbsd.20190326) GENERIC amd64 > > Is there any real use for the monotonically increasing version number > in git? For example, can I go from c27 to git commit hash? Not really / easily; there's no built-in tooling to find the has that corresponds to c260903, although it should be possible to write a script to do so. Really my goal in D20462 is just providing a monotonically increasing number that can serve as a proxy for "is my checkout before/after a specific change?"