Support #1254
Requesting write access
| Status: | Resolved | Start date: | 06/27/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 100% | ||
| Category: | Repository | |||
| Target version: | - |
Description
My public SSH key:
PuTTY-User-Key-File-2: ssh-rsa
Encryption: aes256-cbc
Comment: rsa-key-20120626
Public-Lines: 4
AAAAB3NzaC1yc2EAAAABJQAAAIBai2NUtzLJTP450DZQl2EbUNFyTY3KGSZu656i
zFIaxZ3xd7WdzBqqsRkPaTG2mSF/mMgRHkeFNf6Ol9SR7FyJufAVbZkzlmjea2zj
UEzbRgGFCDiWq+mNpJ5p24S08Y5Uhah5IeI0hq4tUReJZTXw1+wu+7K9hTe4uicR
GIsKxQ==
If I'm not doing this right, please notify me.
History
#2
Updated by divVerent 11 months ago
- Status changed from New to Resolved
Added it.
Apparently, this format is the same as the SSH2 format, as far as ssh-keygen conversion is concerned. Good to know.
Your remote branch names will have to start with "daan/" to be able to be pushed. In case your existing branch is not named that way, you can push it with a command like
git push origin HEAD:daan/hitsoundpitch