Dear Jorge,
On 2019-12-10 10:29, Jorge Fernandez Monteagudo wrote: >> I've been able to push a Bettong board status (commit >> 31848f291a5f9b8ed0cf5e7c2f6651d1b56a1086) > > Sorry, commit edab74e8f3bddbab50fe6160da324fecf0fed329 > > commit edab74e8f3bddbab50fe6160da324fecf0fed329 > Author: Jorge Fernandez <[email protected]> > Date: Mon Dec 9 18:04:16 2019 +0100 > > amd/bettong/4.11-135-gdb945ff860/2019-12-09T16_38_20Z Thank you for the upload. Unfortunately, the used coreboot commit db945ff860 is not in the master branch. ``` coreboot> git show db945ff860 fatal: ambiguous argument 'db945ff860': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' ``` So, nobody will be able to reproduce your result. Kind regards, Paul PS: The board status script should be extended to check, if the used commit is in the master branch.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
