KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

[Andreas Pakulat]

On 20.01.11 19:47:22, Alexander Neundorf wrote:
> On Thursday 20 January 2011, Tom Albers wrote:
> > ----- Original Message -----
> >
> > > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> > > > There is no push/merge/branching policy for KDE. Different projects
> > > > will likely do their own thing. For the time being its just the
> > > > SVN-style development translated to Git.
> > >
> > > words like "unwise", "stupid" and "utterly braindead" come to mind.
> > > you
> > > cannot refer to projects' sovereignty in an environment where
> > > everybody
> > > can push everywhere. and before you make excuses about sysadmin only
> > > implementing and not making decisions: FAIL. at the very least you
> > > should have facilitated the creation of such a policy, because this
> > > very
> > > much *is* part of "implementing git".
> >
> > We facilitate #kde-git and scm-interest mailinglist.
> 
> What's the recommended place to ask git questions ? 
> (I'd prefer a mailing list over IRC)
> scm-interest ?
> 
> Like: how do I check whether my git clone uses the correct ssl-key, and if 
> not, how do I make it use the key ?

A git clone has no idea about ssl keys and such. Git simply runs ssh to
connect to the remote host (if you use the ssh:// protocol). So
configure your ssh client correctly and then you're set.

Andreas

-- 
If you sow your wild oats, hope for a crop failure.