[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22883: Authenticating a Git checkout
From: |
Leo Famulari |
Subject: |
bug#22883: Authenticating a Git checkout |
Date: |
Sun, 5 Jun 2016 17:15:17 -0400 |
User-agent: |
Mutt/1.6.0 (2016-04-01) |
On Sun, Jun 05, 2016 at 03:39:04PM -0500, Christopher Allan Webber wrote:
> One theoretical optimization: if I verify the DAG, could I store
> somewhere that I've verified from commit cabba6e and upward already, so
> the next time I verify it only has to verify the new commits?
AIUI `git verify-commit` takes a single commit as an argument, so you
can pass it an argument like this:
$ git verify-commit $(git rev-list deadbeef..cabba6e)
... and it will only look at those. So, you would tailor the range of
commits that you want to verify.
> Mostly makes sense if we're already going down the only mildly
> crazypants direction of implementing our own tooling :)
It seems you'd want a tool that you trust to store a reference to the
latest commit you trust, and use it to create the range of commits you
pass to `git rev-list`.