[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linuxbios
Subject:    [coreboot] AMD Bettong board status upload (was: AMD Agesa Bettong board support)
From:       Paul Menzel <pmenzel () molgen ! mpg ! de>
Date:       2019-12-10 9:38:09
Message-ID: f1f6b0b2-a89f-f5b2-4185-f87c5db0b980 () molgen ! mpg ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


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 <jorgefm@cirsa.com>
> 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" (application/pkcs7-signature)]

_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org


[prev in list] [next in list] [prev in thread] [next in thread]