Subject: CAcert Code Development list.
List archive
- From: Ian G <iang AT cacert.org>
- To: cacert-devel AT lists.cacert.org
- Subject: Re: creating a patch in new repo style
- Date: Wed, 07 Jul 2010 00:55:27 +1000
- Authentication-results: lists.cacert.org; dkim=pass (1024-bit key) header.i= AT cacert.org; dkim-asp=none
On 7/07/10 12:50 AM, Ian G wrote:
So, following Wytze's instructions, I set up a git repo and created some
sort of patch. See attached. Does this work? How do I check it?
ok, that is a very long file. unexpected!
All I was intending to do was add SecurityPolicy.php and ConfigurationControlSpecification.php to www/policy/ ... but the additional stuff doesn't seem right?! Before installing that in the production system, does it look alright as a patch?
iang
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- creating a patch in new repo style, Ian G, 07/06/2010
- Re: creating a patch in new repo style, Ian G, 07/06/2010
Archive powered by MHonArc 2.6.16.