[git-users] Re: git 1.9.4‏ for window prompt sh.exe: /dev/null No such file or dirctory

[Vasily Makarov]

There is no /dev/null on windows indeed.
You may use Git for windows  or Github for 
windows  to access git CLI on windows.

On Friday, November 14, 2014 10:14:53 AM UTC+3, Thanakorn Sathitwitayakul 
wrote:
>
> I just install git-1.9.4-preview20140929 on my notebook pc, window 7 64 
> bit system. When I run git for the first time I got error message;
>
> sh.exe: /dev/null No such file or directory
>
> When I input some command in git, it run not thing but 
>
> fatal error: 
> sh.exe: /dev/null No such file or directory
>
> I do remove git and reinstall in every possible way, choose different 
> option for different attempt, for many time. Then I did google for the 
> solution to the issue that involve sh.exe or /dev/null on the same os 
> environment. I shut down antivirus before install git. I did install git in 
> safe mode. And all of these doesn't fix the problems.
>
> I appreciate any help
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] On bash doing git add '' troubles

[Philip Oakley]

- Original Message - 
  From: G B 
  To: git-users@googlegroups.com 
  Sent: Friday, November 14, 2014 4:29 PM
  Subject: [git-users] On bash doing git add ''  troubles


  Hello,

  I posted on Stackoverflow 
http://stackoverflow.com/questions/26933761/python-sh-module-and-git-try-to-add-more-files-then-in-command/26934517#26934517
 a problem i was having with python sh.
  It turns out to be a problem with git add.

  When executing git add ''  it sees the empty argument and 
tries to add a random(?) file.

  Is this by design or should i file a bug?

  Thank you.
GB,
you should inlcude all the information. It's likely to be a problem elsewhere. 
I've added a comment to the SO question regarding your need to ensure that the 
CRLF 'fatal:' warning you are getting is resolved.
--
Philip

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Re: Question about chapter "3.1 Git Branching - Branches in a Nutshell" in git docu

[Rick Umali]

On Friday, November 14, 2014 9:22:25 AM UTC-5, Axel Magard wrote:
>
> either I still didn't grasp it or there is a mistake in chapter 3.1 "3.1 
> Git Branching - Branches in a Nutshell" 
> (http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)
>
> The last figure on that page shows that branch 'master' and HEAD are 
> pointing to patch 87ab2, branch 'testing' to c2b9e.
>  
> But the output from git log --oneline --decorate --graph --all 
> shows this:
>
> * c2b9e (HEAD, master) made other changes
> | * 87ab2 (testing) made a change
> |/
> * f30ab add feature #32 - ability to add new formats to the
> * 34ac2 fixed bug #1328 - stack overflow under certain conditions
> * 98ca9 initial commit of my project
>
> Shouldn't it look like this ?
>
> * 87ab2 (HEAD, master) made a change
> | * c2b9e (testing) made other changes
> |/
> * f30ab add feature #32 - ability to add new formats to the
> * 34ac2 fixed bug #1328 - stack overflow under certain conditions
> * 98ca9 initial commit of my project
>
>  
Yes, Alex, I agree with you that there's a mismatch.

The testing pointer (branch) changes from 87ab2 to c2b9e between the 
diagrams labeled "HEAD moves when you checkout" (next to last figure) and 
"Divergent history" (last figure). I believe the git log is correct.

Rick Umali / Author: "Learn Git in a Month of Lunches" / 
www.manning.com/umali

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Question about chapter "3.1 Git Branching - Branches in a Nutshell" in git docu

[Axel Magard]

Hi folks,
either I still didn't grasp it or there is a mistake in chapter 3.1 "3.1 
Git Branching - Branches in a Nutshell" 
(http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)

The last figure on that page shows that branch 'master' and HEAD are 
pointing to patch 87ab2, branch 'testing' to c2b9e.
 
But the output from git log --oneline --decorate --graph --all 
shows this:

* c2b9e (HEAD, master) made other changes
| * 87ab2 (testing) made a change
|/
* f30ab add feature #32 - ability to add new formats to the
* 34ac2 fixed bug #1328 - stack overflow under certain conditions
* 98ca9 initial commit of my project

Shouldn't it look like this ?

* 87ab2 (HEAD, master) made a change
| * c2b9e (testing) made other changes
|/
* f30ab add feature #32 - ability to add new formats to the
* 34ac2 fixed bug #1328 - stack overflow under certain conditions
* 98ca9 initial commit of my project

Cheers ... Axel Magard

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] On bash doing git add '' troubles

[G B]

Hello,

I posted on Stackoverflow 
http://stackoverflow.com/questions/26933761/python-sh-module-and-git-try-to-add-more-files-then-in-command/26934517#26934517
 
a problem i was having with python sh.
It turns out to be a problem with git add.

When executing git add ''  it sees the empty argument 
and tries to add a random(?) file.

Is this by design or should i file a bug?

Thank you.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] git 1.9.4‏ for window prompt sh.exe: /dev/null No such file or dirctory

[Dale R. Worley]

> From: Thanakorn Sathitwitayakul 
> 
> I just install git-1.9.4-preview20140929 on my notebook pc, window 7 64 bit 
> system. When I run git for the first time I got error message;
> 
> sh.exe: /dev/null No such file or directory
> 
> When I input some command in git, it run not thing but 
> 
> fatal error: 
> sh.exe: /dev/null No such file or directory
> 
> I do remove git and reinstall in every possible way, choose different 
> option for different attempt, for many time. Then I did google for the 
> solution to the issue that involve sh.exe or /dev/null on the same os 
> environment. I shut down antivirus before install git. I did install git in 
> safe mode. And all of these doesn't fix the problems.
> 
> I appreciate any help

Have you checked to see that /dev/null exists on your system?

My understanding is that you can only run Git in a Unix-like
environment.  It appears that whatever provides the Unix-like
environment on your Windows 7 system is not providing /dev/null.

Dale

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] git 1.9.4‏ for window prompt sh.exe: /dev/null No such file or dirctory

[Thanakorn Sathitwitayakul]

I just install git-1.9.4-preview20140929 on my notebook pc, window 7 64 bit 
system. When I run git for the first time I got error message;

sh.exe: /dev/null No such file or directory

When I input some command in git, it run not thing but 

fatal error: 
sh.exe: /dev/null No such file or directory

I do remove git and reinstall in every possible way, choose different 
option for different attempt, for many time. Then I did google for the 
solution to the issue that involve sh.exe or /dev/null on the same os 
environment. I shut down antivirus before install git. I did install git in 
safe mode. And all of these doesn't fix the problems.

I appreciate any help

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Re: Unable to install Git after building _everything_

[Pierre-François CLEMENT]

On Thursday, 18 October 2012 23:58:56 UTC+2, Yves S. Garret wrote:
>
> Yes, but vetoed the idea.  For one I'm not a fan of Windows + Git 
> "integration".  Second of all, I prefer to work from the command line.
>
> I'll look into the pre-built libraries tomorrow when I'm at the office, 
> thanks.
>
> On Wednesday, October 17, 2012 2:53:48 PM UTC-4, Thomas Ferris Nicolaisen 
> wrote:
>>
>> This may be a silly question, but did you consider just using msysgit 
>> ?
>>  
>> If you still want to use Cygwin-Git, there are some pre-built binaries 
>>  for it, I believe.
>>
>
As Thomas stated, using Cygwin's pre-built git binary package is probably 
the simplest solution indeed. However, if you still want to compile Git 
from source on Cygwin because you need or want the latest version, just 
install the dependencies you need using Cygwin's installer -- in that case, 
docbook2x 
(Cygwin package) 
. 
Each time the build fails, check wether what you miss is available through 
Cygwin's installer and install it if it is. With a little luck you may end 
up with a successful build eventually :)

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.