On Tuesday 20 March 2012 21:20:38 Ivanko B wrote:
> Done, announced.
>
Google translates it as
"Martin bungled frontend to GIT-y"
I hope it translates wrong. Otherwise you will experience consequences. ;-)
Martin
--
This
On Tuesday 20 March 2012 21:20:38 Ivanko B wrote:
> Done, announced.
>
Thanks, please add the provided screenshots.
Martin
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/
Did you try ssh command in windows console with -v in order to get more info?
=
Me'm chasing Internet for a decent tutorial :)
2012/3/21, Ivanko B :
> Done, announced.
>
>
> 2012/3/20, Martin Schreiber :
>> On Tuesday 20 March 2012 16:40:47 Ivanko B wrote:
>>> Hmm, it seems that the ta
Done, announced.
2012/3/20, Martin Schreiber :
> On Tuesday 20 March 2012 16:40:47 Ivanko B wrote:
>> Hmm, it seems that the task of SSH login from non-latin win-32 clients
>> to LINUX GIT repo can't be accomplished since server-side SSH refuses
>> to accept non-latin user names within public key
Hmm, it seems that the task of SSH login from non-latin win-32 clients
to LINUX GIT repo can't be accomplished since server-side SSH refuses
to accept non-latin user names within public keys generated by
"../git/bin/ssh-keygen -t rsa".
2012/3/20, Martin Schreiber :
> Am 20.03.2012 11:29, schrieb
Am 20.03.2012 11:29, schrieb Martin Schreiber:
>> or setup the environment that SSH finds the keys
>> in\\.ssh.
>> ===
>> Which variable ?
>>
> Probably "E:\Programme\Git\.ssh\config"-"IdentityFile". Hmm for me this
> entry is the automatically created
> "
> IdentityFile "/C/Dokumente u
Am 20.03.2012 11:45, schrieb Ivanko B:
> If you are on windows you probably must copy the SSH keys into .ssh of the SSH
> installation home directory
> ===
> "GIT CLONE" complains that it can't create "/.ssh/" within
> "/C/Documents and Settings/МУ_NAME_IN_RUSSIAN/". Me even created ths
If you are on windows you probably must copy the SSH keys into .ssh of the SSH
installation home directory
===
"GIT CLONE" complains that it can't create "/.ssh/" within
"/C/Documents and Settings/МУ_NAME_IN_RUSSIAN/". Me even created thsi
directory by myself & put into it known_host &
On Tuesday 20 March 2012 10:20:27 Ivanko B wrote:
>
> PS:
> Are any heavy changes to TMSESQLQuery's offline mode ? Possibly, me'll need
> it.
>
Not since 2.8 IIRC.
Martin
--
This SF email is sponsosred by:
Try Windows Azu
On Tuesday 20 March 2012 10:20:27 Ivanko B wrote:
> Login problem?
> ===
> Most possibly. Me'll try to switch to RSA kyes auth.
>
If you are on windows you probably must copy the SSH keys into .ssh of the SSH
installation home directory or setup the environment that SSH finds the keys
git gui'
=
It assumes deep knowlefge of GIT mechanics :) Then it's easier to use
the console "git".
2012/3/20, Ivanko B :
> Login problem?
> ===
> Most possibly. Me'll try to switch to RSA kyes auth.
>
> PS:
> Are any heavy changes to TMSESQLQuery's offline mode ? Possibly
Login problem?
===
Most possibly. Me'll try to switch to RSA kyes auth.
PS:
Are any heavy changes to TMSESQLQuery's offline mode ? Possibly, me'll need it.
2012/3/20, Martin Schreiber :
> Ivanko B wrote:
>
>> At me MSEgit only sees remote "origin" branch as long as "git clone"
>> cr
Ivanko B wrote:
> At me MSEgit only sees remote "origin" branch as long as "git clone"
> created local "master" branch. So, me created local "origin" branch
> so that it matches the remote "origin" then retried "commit" & "push"
> but failed with "fatal: The remote end hung up unexpectedly".
>
L
On 20 March 2012 10:11, Ivanko B wrote:
> At me MSEgit only sees remote "origin" branch as long as "git clone"
> created local "master" branch. So, me created local "origin" branch
> so that it matches the remote "origin" then retried "commit" & "push"
> but failed with "fatal: The remote end hun
At me MSEgit only sees remote "origin" branch as long as "git clone"
created local "master" branch. So, me created local "origin" branch
so that it matches the remote "origin" then retried "commit" & "push"
but failed with "fatal: The remote end hung up unexpectedly".
2012/3/20, Graeme Geldenhuy
On 20 March 2012 09:36, Ivanko B AFAIK, it's correct to start filling an empty repo via
> commits from its clones.
Yes, that is normal usage with git.
I just tried with MSEgit. Cloned a repository from a empty bare
repository. I could do a local commit in my cloned repository via
MSEgit, but I
On Tuesday 20 March 2012 08:36:40 Ivanko B wrote:
> BTW, me had to clone via the console command "git clone
> git://192.168.1.5/var/cache/git/podpiska_pg_git" (MSEgui refused to do
> that for some reason because failed "git clone" call ) where "git init
> --bare" were called on the remote server wi
BTW, me had to clone via the console command "git clone
git://192.168.1.5/var/cache/git/podpiska_pg_git" (MSEgui refused to do
that for some reason because failed "git clone" call ) where "git init
--bare" were called on the remote server within its
"/var/cache/git/podpiska_pg_git/" directory to cr
18 matches
Mail list logo
