Stephan,
What is the current status of the revision control system? Are we going to use the tla now?
Ollie
* Li-Ta Lo ollie@lanl.gov [050316 22:51]:
Stephan,
What is the current status of the revision control system? Are we going to use the tla now?
After quite some delay, commits to the gnu arch repository work now as well.
The Download page in Wiki has some information on public downloading of the archive. We should add the developers information to a seperate page once everything has settled
http://wiki.linuxbios.org/index.php/Download_freebios_v2
Stefan
On Wed, 2005-03-16 at 17:18, Stefan Reinauer wrote:
- Li-Ta Lo ollie@lanl.gov [050316 22:51]:
Stephan,
What is the current status of the revision control system? Are we going to use the tla now?
After quite some delay, commits to the gnu arch repository work now as well.
The Download page in Wiki has some information on public downloading of the archive. We should add the developers information to a seperate page once everything has settled
http://wiki.linuxbios.org/index.php/Download_freebios_v2
Stefan
How updated is you tla archive? I think there are changes on the CVS.
BTW, do I have to send you my gpg key to get commit privilege? Or ssh key is enough.
Ollie
* Li-Ta Lo ollie@lanl.gov [050317 19:11]:
How updated is you tla archive? I think there are changes on the CVS.
The latest commit was your x86emu fixes on 2005-03-10
http://www.openbios.org/cgi-bin/viewarch.cgi/linuxbios@linuxbios.org--devel/... (rather slow due to about 1000 changesets. i am discussing this issue with the author of viewarch.)
BTW, do I have to send you my gpg key to get commit privilege? Or ssh key is enough.
It is enough to use ssh. THOUGH: It is highly recommended that you sign the commits so that the origin can be verified. (ie otherwise I could in theory fake a commit done by you)
Stefan
On Thu, 17 Mar 2005, Stefan Reinauer wrote:
It is enough to use ssh. THOUGH: It is highly recommended that you sign the commits so that the origin can be verified. (ie otherwise I could in theory fake a commit done by you)
to make sure I understand: if I have a gpgkey, then the commit process will automagically ensure that it is signed, which is not the case for sshkey?
ron
"Ronald G. Minnich" rminnich@lanl.gov writes:
On Thu, 17 Mar 2005, Stefan Reinauer wrote:
It is enough to use ssh. THOUGH: It is highly recommended that you sign the commits so that the origin can be verified. (ie otherwise I could in theory fake a commit done by you)
to make sure I understand: if I have a gpgkey, then the commit process will automagically ensure that it is signed, which is not the case for sshkey?
These issues are orthogonal.
The ssh key provides write access to the repository through sftp. By chance this is the easiest way to implement a shared archive.
The gpg key (which is mandatory on a signed arch archive like linuxbios@linuxbios.org--devel) allows people to check to see if it was really you who committed the change.
So you just need the ssh key to talk to Stefan box at openbios.org
Eric
* Ronald G. Minnich rminnich@lanl.gov [050317 22:35]:
It is enough to use ssh. THOUGH: It is highly recommended that you sign the commits so that the origin can be verified. (ie otherwise I could in theory fake a commit done by you)
to make sure I understand: if I have a gpgkey, then the commit process will automagically ensure that it is signed, which is not the case for sshkey?
You have to do the following: $ mkdir -p ~/.arch-params/signing $ echo "gpg --clearsign" > ~/.arch-params/signing/=default $ echo "gpg --verify-files -" > ~/.arch-params/signing/=default.check
* gpg is only there to proof integrity of the checkins * ssh only gives you access to the machine
Stefan
-
ebiederman＠lnxi.com -
Li-Ta Lo -
Ronald G. Minnich -
Stefan Reinauer