Hey Sinny and Ben ,
I have uploaded a new ssh key and mailed sysad...@kde.org
Regards
On Sat, Jun 8, 2013 at 10:41 AM, Sinny Kumari wrote:
> I am assuming that you have kde developer account.
>
> Have you added your public key on https://identity.kde.org/ ?
> If not, login to https://identity
I am assuming that you have kde developer account.
Have you added your public key on https://identity.kde.org/ ?
If not, login to https://identity.kde.org/ and add your public key in
"manage SSH keys" section.
After adding public key, tell sysadmin about changes done on #sysadmin or
sysadmin (sys
Hi Heena,
I would suggest ensuring that the appropriate SSH keys are uploaded to
your Identity account as a first step.
Regards,
Ben
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
I am getting an error on pushing to kde-workspace
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
on heena@heena:~/kde-workspace/plasma/desktop/applets/Windowlist/contents/qml$
git push kde:kde-workspace heenamahour/window-list:heenamahour/window-list
Kindly suggest somet
On Fri, Jun 7, 2013 at 12:37 PM, Jeremy Whiting wrote:
>
> David,
>
> Yes if you could do the same change in git that would be best.
>
> thanks,
Done. In fact, my commit message in SVN had a wrong date and I had a
chance to fix it because of this, so definitely not a bug but a
feature :) Thanks!
Some problems were reported with the 2.8.11 release. Thanks to the
swift work of Brad King, Stephen Kelly, Rolf Eike Beer and Modestas
Vainius, those problems have been fixed. We've prepared a 2.8.11.1 bug
fix release to address those issues.
The change log page for this bug-fix only release is he
Am Freitag, 7. Juni 2013, 11:38:52 schrieb Jeremy Whiting:
> Urs,
>
> I think we are good to go now. I believe scripty got confused because
> there was still content in svn and git. Albert would know more though.
> And yeah, I think replacing only on trunk is enough iirc.
>
> BR,
> Jeremy
>
>
Urs,
I think we are good to go now. I believe scripty got confused because
there was still content in svn and git. Albert would know more though.
And yeah, I think replacing only on trunk is enough iirc.
BR,
Jeremy
On Fri, Jun 7, 2013 at 12:07 AM, Urs Wolfer wrote:
> Kopete looks now also
David,
Yes if you could do the same change in git that would be best.
thanks,
Jeremy
On Fri, Jun 7, 2013 at 6:32 AM, David Narvaez wrote:
> On Wed, Jun 5, 2013 at 4:37 PM, Jeremy Whiting wrote:
> >
> > Urs,
> >
> > Ok, kdenetwork-filesharing, kdenetwork-strigi-analyzers, kdnssd, kget,
> > kpp
On Thursday 06 June 2013 22:44:18 Albert Astals Cid wrote:
> El Dijous, 6 de juny de 2013, a les 22:26:17, Pali Rohár va
escriure:
> > Hello,
> >
> > all kopete repos were pushed to git.kde.org. I also enabled
> > hooks and development sites and configured trunk i18n
> > branch.
> >
> > When you
On Wed, Jun 5, 2013 at 4:37 PM, Jeremy Whiting wrote:
>
> Urs,
>
> Ok, kdenetwork-filesharing, kdenetwork-strigi-analyzers, kdnssd, kget,
> kppp, krdc and krfb pushed, tags pushed, hooks enabled, i18n branches set in
> projects.kde.org settings, and they are enabled for development.
> After kopete
I'm the maintainer of KRDC. Sorry for not confirming this request. I
have done so now.
Though this does not mean that I will implement it in the next weeks. ;)
Bye
urs
On 2013-06-06 18:46, Myriam Schweingruber wrote:
Forwarding to kde-devel@, as it is more likely to be answered where
the dev
12 matches
Mail list logo
