You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
And I think that this DESCRIPTION is insufficient to try to debug it. In the least, the output with GIT_TRACE=1 would be required, and then it would still take more effort on the reporters side to start REMOTELY to equal the effort asked from others to help this issue.
I mean, you got a beautiful software for free -- even if it contains bugs -- and then you throw a one-liner bug report at the good people doing all the work, basically asking them to spend yet more time, much more time on the bug than you did. I guess you can count me out.
@fatjyc have you even bothered to follow the link I pasted? If you actually did, have you followed the instructions? If you did that, too, did it fix the problem you tried to report? If so, was I "able to know the problem"?
I closed the pull request because somebody else gave me the feedback that my fix works. @fatjyc please take this as an encouragement to do substantially better next time. That someone giving useful feedback could have been you...
I'm probably going to regret doing this. I only came upon this because I ran into the same issue with msysgit, but hopefully someone will read this and benefit.
@fatjyc - I can only speak for myself and not @dscho. However, I hope you realize one day that your posts made you look incredibly rude and ungrateful for the hours of thankless work people have volunteered in this project. Your tone was especially offensive considering that git is not officially supported on Windows by the authors of git and it presents unique issues not found on other operating systems, such as this.
First, you initially provide only one line console output which did not help solve the issue. Second, after someone asked for more information, you only provide the command you typed in and then put "BUG" and "THX." Writing words with all capital letters is probably the worst thing you can do on the Internet because it is equivalent to yelling at someone. Third, you accused someone of misinterpretation.
At no point, did you provide anything useful towards a solution. When you were asked to help further, you did not do so and only restated your problem. If you didn't know how to be more helpful, you could have asked how to be more helpful. Even if you said "I tried ssh and that worked for me," that would have been infinitely more helpful than what you wrote. You gave an impression of entitlement.
I want to stress again that people do this for free, and it's discouraging when it is not appreciated. You may not have felt this way, but I see no other way to interpret your posts.
Did anyone every consider that @fatjyc didn't know about the GIT_TRACE=1 property?
Sure he could have run it after it was mentioned, but we don't know what his level of knowledge is. Perhaps a friendlier:
"hey we need some more information can you run this [Command] and paste back what it says" would have solved this whole issue.
I think there was rudeness on both sides here.
We all understand that git is free and an awesome piece of software, but not everyone that uses it is as knowledgeable as we would like.
Note: I am in now way saying that his use of all caps was allowable, just making a point that he might not of had the knowledge to provide the information you wanted and a little more guidance probably would have helped him out.
@birdwing have you actually read this thread? And estimated how much time the respective parties spent? If so, color me speachless as to how you could possibly write what you wrote.
I noticed that the 4th post down on the same day this issue was opened you posted angrily towards him for not providing enough information in his description. Nowhere before your post was any information offered to him to tell him how to obtain the information.
That's what i noticed.
There was defensiveness and wrong posting on both sides. I was only pointing out an observation on how all the anger may have been avoided.
Activity
t-b commentedon Jan 3, 2014
Please post a minimal working example including the initial git clone of a public repository.
fatjyc commentedon Jan 3, 2014
I have a private project in bitbucket.
I upgrade Git-1.8.5.2-preview20131230.
I can't clone the project for http way.
I think this is a BUG.
THX
dscho commentedon Jan 3, 2014
And I think that this DESCRIPTION is insufficient to try to debug it. In the least, the output with
GIT_TRACE=1would be required, and then it would still take more effort on the reporters side to start REMOTELY to equal the effort asked from others to help this issue.I mean, you got a beautiful software for free -- even if it contains bugs -- and then you throw a one-liner bug report at the good people doing all the work, basically asking them to spend yet more time, much more time on the bug than you did. I guess you can count me out.
Do not use _wfopen() for DOS device filenames
dscho commentedon Jan 3, 2014
@fatjyc there is a way to redeem yourself: follow the instructions at the end of https://groups.google.com/d/msg/msysgit/s4dB8Nv9V4c/55-cGPdPYmAJ and report back whether that fixes the issue.
fatjyc commentedon Jan 4, 2014
@dscho
I think that you misunderstood what I meant.
I just hope you will be able to know the problem.
dscho commentedon Jan 4, 2014
@fatjyc have you even bothered to follow the link I pasted? If you actually did, have you followed the instructions? If you did that, too, did it fix the problem you tried to report? If so, was I "able to know the problem"?
dscho commentedon Jan 6, 2014
I closed the pull request because somebody else gave me the feedback that my fix works. @fatjyc please take this as an encouragement to do substantially better next time. That someone giving useful feedback could have been you...
Danation commentedon Jan 14, 2014
Please forgive me if I'm out of line, but I am writing to confirm that this fix worked for me as well. Thank you!
mouyang commentedon Jan 16, 2014
I'm probably going to regret doing this. I only came upon this because I ran into the same issue with msysgit, but hopefully someone will read this and benefit.
@fatjyc - I can only speak for myself and not @dscho. However, I hope you realize one day that your posts made you look incredibly rude and ungrateful for the hours of thankless work people have volunteered in this project. Your tone was especially offensive considering that git is not officially supported on Windows by the authors of git and it presents unique issues not found on other operating systems, such as this.
First, you initially provide only one line console output which did not help solve the issue. Second, after someone asked for more information, you only provide the command you typed in and then put "BUG" and "THX." Writing words with all capital letters is probably the worst thing you can do on the Internet because it is equivalent to yelling at someone. Third, you accused someone of misinterpretation.
At no point, did you provide anything useful towards a solution. When you were asked to help further, you did not do so and only restated your problem. If you didn't know how to be more helpful, you could have asked how to be more helpful. Even if you said "I tried ssh and that worked for me," that would have been infinitely more helpful than what you wrote. You gave an impression of entitlement.
I want to stress again that people do this for free, and it's discouraging when it is not appreciated. You may not have felt this way, but I see no other way to interpret your posts.
LongLiveCHIEF commentedon Jan 22, 2014
@mouyang 👍 💯
birdwing commentedon Jan 30, 2014
Did anyone every consider that @fatjyc didn't know about the GIT_TRACE=1 property?
Sure he could have run it after it was mentioned, but we don't know what his level of knowledge is. Perhaps a friendlier:
"hey we need some more information can you run this [Command] and paste back what it says" would have solved this whole issue.
I think there was rudeness on both sides here.
We all understand that git is free and an awesome piece of software, but not everyone that uses it is as knowledgeable as we would like.
Note: I am in now way saying that his use of all caps was allowable, just making a point that he might not of had the knowledge to provide the information you wanted and a little more guidance probably would have helped him out.
dscho commentedon Jan 30, 2014
@birdwing have you actually read this thread? And estimated how much time the respective parties spent? If so, color me speachless as to how you could possibly write what you wrote.
birdwing commentedon Jan 31, 2014
I noticed that the 4th post down on the same day this issue was opened you posted angrily towards him for not providing enough information in his description. Nowhere before your post was any information offered to him to tell him how to obtain the information.
That's what i noticed.
There was defensiveness and wrong posting on both sides. I was only pointing out an observation on how all the anger may have been avoided.
I did not mean to offend anyone
dscho commentedon Jan 31, 2014
@birdwing okay. Now can we please move on?
adamralph commentedon Feb 17, 2014
Is this fix likely to be released soon?
dscho commentedon Feb 17, 2014
@adamralph have a look at the mailing list.