git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Bash Bug

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 14, 2017, 14:28 UTC
Message-ID
<alpine.DEB.2.21.1.1707141625150.4193@virtualbox>
In-Reply-To
<CAAu0pLedy5xqUgF7drMf=tQgMJD4rXq+JvKaiE54EdRFZWuTkQ@mail.gmail.com>
Hi Kavita,
On Fri, 14 Jul 2017, Kavita Desai wrote:
> Originally, when I first had Git Bash everything was working
> perfectly. Randomly one day, my bash commands were not working.

There are a gazillion ways how commands can "not work". You *need* to be more specific here. In the least, a precise pasted output of a failed command is necessary.

In addition, a couple of other points of interest would be good to know, the issue reporting template at https://github.com/git-for-windows/git/issues/new tries to help you provide as much important information as you can. Maybe give it a try?

Ciao, Johannes

Previous: Kavita DesaiNext: Kavita Desai
Message 2 of 9 in “Git Bash Bug”
  1. Kavita DesaiJul 14, 2017
  2. Johannes SchindelinJul 14, 2017
  3. Kavita DesaiJul 14, 2017
  4. Paul SmithJul 14, 2017
  5. Kavita DesaiJul 14, 2017
  6. Paul SmithJul 14, 2017
  7. Johannes SchindelinJul 14, 2017
  8. Paul SmithJul 14, 2017
  9. Johannes SchindelinJul 14, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.