RE: "git log" does not display refs info when executed via C# Process class on Windows

Thanks, I will try that as well. Strange it works on command line but not STDOUT though. -Original Message- From: Junio C Hamano Sent: Friday, August 9, 2019 5:50 PM To: Cliff Schomburg Cc: SZEDER Gábor ; git@vger.kernel.org Subject: Re: "git log" does not display refs

RE: "git log" does not display refs info when executed via C# Process class on Windows

standard output again. Only on the command line. Does --decorate-refs not return to STDOUT? Thanks, Cliff -Original Message- From: SZEDER Gábor Sent: Friday, August 9, 2019 3:51 PM To: Cliff Schomburg Cc: git@vger.kernel.org Subject: Re: "git log" does not display refs info when ex

RE: "git log" does not display refs info when executed via C# Process class on Windows

Adding --decorate gave me the desired result. Thanks for your help! -Original Message- From: SZEDER Gábor Sent: Friday, August 9, 2019 3:51 PM To: Cliff Schomburg Cc: git@vger.kernel.org Subject: Re: "git log" does not display refs info when executed via C# Process class

"git log" does not display refs info when executed via C# Process class on Windows

ssue? Any idea why the output to CMD and STDOUT would be different? Thanks, Cliff

RE: Simple shortcut for "git push --set-upstream origin newBranchName"

dows CMD prompt, if that matters at all. Thanks,m Cliff -Original Message- From: Cliff Schomburg Sent: Friday, May 31, 2019 11:13 AM To: Patryk Obara ; git@vger.kernel.org Subject: RE: Simple shortcut for "git push --set-upstream origin newBranchName" Thanks, Patryk. It&#x

RE: Simple shortcut for "git push --set-upstream origin newBranchName"

Thanks, Patryk. It's always nice to see the feature I want is already implemented! 😊 -Original Message- From: Patryk Obara Sent: Friday, May 31, 2019 11:05 AM To: Cliff Schomburg ; git@vger.kernel.org Subject: Re: Simple shortcut for "git push --set-upstream origin new

RE: Simple shortcut for "git push --set-upstream origin newBranchName"

Wow, I did not see that in the man pages... but I see it now. Thanks! So I guess I would change my ask to this: "git push -u" Should default to "origin branch" if no parameters are provided. Thoughts? Thanks, Cliff -Original Message- From: Patryk Obara Sent:

RE: Simple shortcut for "git push --set-upstream origin newBranchName"

Resending as plain text From: Cliff Schomburg Sent: Thursday, May 30, 2019 6:29 PM To: git@vger.kernel.org Subject: Simple shortcut for "git push --set-upstream origin newBranchName" Hi all, This is more of a suggestion than a bug report. I create new topic branches quite frequentl

Git case-sensitivity bug

I believe I have discovered a bug with git tools. If you create a git branch, you can refer to that branch with case-insensitive alterations and it will track as the same branch. If I create branch "test" I cannot then create branch "Test" because the same name is already used. However, git comm

Git server memory requirements

trade off some speed for less memory if we can) before upgrading. Thanks, Cliff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html