Thank you. I think we ought to demand a product recall for everything Intel.
signature.asc
Description: PGP signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Bring it up at the next meeting? Who can edit the meeting agenda?
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXM+DONBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs
ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmOD1BAAtKDluafigaFg21VK
353
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
David, perhaps we can apply templates based on category? And then add or remove
individual items to and from categories as things change?
Just a thought.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXM9fkNBxLdXNoYWwgSGFkYSAoZGV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Question to older members: What has been your experience with coverity and
openwrt? Was it useful to you in the past? Is this something that we would like
to continue to do going forward?
Sincerely,
-BEGIN PGP SIGNATURE-
Version: APG v1.1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Git mirror also at https://gitlab.com/lede
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXL4aCNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs
ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmNfKg/+LlyVX5D1Xo38/Xbt
KPN9bPsKY7cF3Ts9e4s9Q+F50U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Perhaps signing merge commits is good enough. It wouldn't require new
contributors to do something more and it will be easier to keep track of the
public keys for a small group of people.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel, I like what you said. I hinted something like that in the original
message.
I don't like the idea of making changes to history after it is published.
Personally, I don't care about commit pollution but if the team thinks it is
important,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Regarding signing commits with GPG key, it would be nice to recommend it but
> making it a requirement sounds like a barrier.
I'd argue such a barrier is OK if we want to quickly increase the size of the
team of people with commit access. I thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Ben,
Just to be clear. We're talking about signing git commits, not emails. I
apologize for my ugly emails though.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXK1jsNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs
ZGV2ZWxvcGVyQG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My original thought was to allow us to grant many people commit access.
Signing commits won't solve everything. There are other, arguably more
important things, to do like code reviews and automated unit as well as device
tests as well as manual t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I love this idea. A wiki with pages for each router :D and people who have that
particular machine can come in and write about the quirks about it. It will be
great!
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXKscxNBxLdXNoYWw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Jo,
Never done it in a real project. Signing commits should not make things any
worse. The worst thing that can happen as far as I know is we are back to where
we are today.
Rewriting history can be a pain from what I've read. However, I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Greetings
I'd like to propose that all commits (at least to master) going forward be
signed with the commiter's gpg key.
https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
Thoughts?
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you, Ted. I've started a mirror on gitlab. It should fetch commits every
hour. https://gitlab.com/groups/lede
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBCgA7BQJXKjhCNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs
ZGV2ZWxvcGVyQGdtY
14 matches
Mail list logo
