On 15 May 2012 11:51, IvankoB ivankob4m...@gmail.com wrote:
The Qs were where these correct places are in different setups ? (it
took tries errors ) how to bypass the non-latin etc limitations?
(hardly documented even about they are).
On all the Windows setups I have worked on (Win2k, XP
Am 16.05.2012 11:13, schrieb Graeme Geldenhuys:
On 15 May 2012 11:51, IvankoBivankob4m...@gmail.com wrote:
The Qs were where these correct places are in different setups ? (it
took tries errors ) how to bypass the non-latin etc limitations?
(hardly documented even about they are).
On
On 16 May 2012 11:34, Martin Schreiber mse00...@gmail.com wrote:
The last git install exe I used expects the keys in
E:\Programme\Git\.ssh. In install dialog I changed the install
directory from C:... to E:
Interesting I'm still using 1.7.3.1 on all my Windows VM's.
--
Regards,
-
E:\Programme\Git\.ssh
GIT ignores it unless directed to use.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can
On 14 May 2012 11:08, Martin Schreiber mse00...@gmail.com wrote:
On Monday 14 May 2012 10:32:03 IvankoB wrote:
Do you know the .gitignore file?
Project wide too ? What for this doubling..
Valid for the directory and subdirectories without .gitignore files. You
should not touch the files in
For instance:
# git ls-files --others --exclude-from=.git/info/exclude
# Lines that start with '#' are comments.
# For a project mostly in C, the following would be a good set of
# exclude patterns (uncomment them if you want to use them):
# *.[oa]
# *~
*.exe
*.a
*.o
Do you know the .gitignore file?
Project wide too ? What for this doubling..
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how
On Monday 14 May 2012 10:32:03 IvankoB wrote:
Do you know the .gitignore file?
Project wide too ? What for this doubling..
Valid for the directory and subdirectories without .gitignore files. You
should not touch the files in .git, it is better to use git commands to
change settings.
it is better to use git commands to
change settings.
These must be read out from the huge GIT doc massive :)
PS:
It was a real nigtmare to get working SSH-redy (no password requests)
GIT repo (GitoSis) in our LAN...Me spent a day + a half on it !
2012/5/14, Martin Schreiber
Am 14.05.2012 12:33, schrieb Ivanko B:
it is better to use git commands to
change settings.
These must be read out from the huge GIT doc massive :)
PS:
It was a real nigtmare to get working SSH-redy (no password requests)
GIT repo (GitoSis) in our LAN...Me spent a day + a
Yup, on client side especially on Windows where OpenSSH does not request
passwords for private keys from pipes.
Win32's SSH is a nightmare too. It requires key path to be ANSI no-space
as long as still requires it to be user home directory which is
space-containing non-latin at me. The
11 matches
Mail list logo
