Re: Bug Report: git status triggers a file change event

Hi all, On Thu, 22 Feb 2018, Stefan Beller wrote: > On Wed, Feb 21, 2018 at 9:22 PM, Jonathan Nieder wrote: > > +git-for-windows First of all, this is clearly not a Windows-specific problem, as the index file *is* updated, and that is simply the same behavior as on

Re: Bug Report: git status triggers a file change event

On Wed, Feb 21, 2018 at 9:22 PM, Jonathan Nieder wrote: > +git-for-windows > Hi, > > Raining Chain wrote: > >> On Windows 10, git version 2.16.2.windows.1, running the command >> >> git status >> >> will trigger a file change event to file C:\myPath\.git "Attributes >>

Re: Bug Report: git status triggers a file change event

+git-for-windows Hi, Raining Chain wrote: > On Windows 10, git version 2.16.2.windows.1, running the command > > git status > > will trigger a file change event to file C:\myPath\.git "Attributes changed." > > This causes problems when using scripts that detect file changes such > as tsc -w

Bug Report: git status triggers a file change event

On Windows 10, git version 2.16.2.windows.1, running the command git status will trigger a file change event to file C:\myPath\.git "Attributes changed." This causes problems when using scripts that detect file changes such as tsc -w (Typescript compiler) and using softwares that regularly

Re: Bug#757297: 'git status' output is confusing after 'git add -N'

Duy Nguyen pclo...@gmail.com writes: On Thu, Aug 7, 2014 at 7:34 AM, Jonathan Nieder jrnie...@gmail.com wrote: Package: git Version: 1:2.0.0-1 Tags: upstream $ git init foo Initialized empty Git repository in /tmp/t/foo/.git/ $ cd foo $ echo hi README $ git add -N README $

Re: Bug#757297: 'git status' output is confusing after 'git add -N'

On Thu, Aug 7, 2014 at 7:34 AM, Jonathan Nieder jrnie...@gmail.com wrote: Package: git Version: 1:2.0.0-1 Tags: upstream $ git init foo Initialized empty Git repository in /tmp/t/foo/.git/ $ cd foo $ echo hi README $ git add -N README $ git status On branch master

Re: Aw: Re: Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

The following message is a courtesy copy of an article that has been posted to gmane.comp.version-control.git as well. Junio C Hamano gits...@pobox.com writes: Thomas Ackermann th.ac...@arcor.de writes: But for the simple use case where you only have a master branch I consider it not really

Aw: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

th.ac...@arcor.de Datum: 06.01.2014 06:31 Betreff: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master' 2014/1/5 Thomas Ackermann th.ac...@arcor.de: Since f223459 status: always show tracking branch even no change 'git status' (and 'git checkout master

Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

correctly reports you're behind. --- Thomas - Original Nachricht Von: Jiang Xin worldhello@gmail.com An: Thomas Ackermann th.ac...@arcor.de Datum: 06.01.2014 06:31 Betreff: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master

Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

2014/1/6 Thomas Ackermann th.ac...@arcor.de: Hi Jiang, this happens with all of my repo clones (I am using V1.8.5.2 on Windows and on Linux). Steps to reproduce: mkdir repo_a cd repo_a git init . echo 1foo git add foo git commit -m 1 cd .. git clone repo_a repo_b cd repo_a echo

Aw: Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

Unfortunately that's not true. In repo_b your ref for origin/master has not moved. It has remotely (meaning refs/heads/master in repo_a has moved), but git status is not hitting the remote to find out; it only looks at the local state. To see what I mean, run git fetch in repo_b. Once you

Re: Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

Hi, Thomas Ackermann wrote: In repo_b your ref for origin/master has not moved. It has remotely (meaning refs/heads/master in repo_a has moved), but git status is not hitting the remote to find out; it only looks at the local state. [...] But for the simple

Aw: Re: Re: Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

But for the simple use case where you only have a master branch I consider it not really helpful and - at least for me - misleading. I see what you mean, and you're not the only one. Git follows a rule of never contact another machine unless explicitly asked to using a command such

Re: [Bug report] 'git status' always says Your branch is up-to-date with 'origin/master'

2014/1/5 Thomas Ackermann th.ac...@arcor.de: Since f223459 status: always show tracking branch even no change 'git status' (and 'git checkout master' always says Your branch is up-to-date with 'origin/master' even if 'origin/master' is way ahead from local 'master'. Hi, Thomas Can you

Bug in git status

I think I have found a bug in git status --untracked-files=all --ignored, in both 1.8.0 and in master: $ git init status-test Initialized empty Git repository in /home/mhagger/self/proj/git/status-test/.git/ $ cd status-test $ touch x $ touch x.ignore-me $ mkdir y $ touch y/foo $ touch y

bug report: git status --porcelain inconsistent quoting

mkdir D cd D git init Initialized empty Git repository in /tmp/D/.git/ echo 1 with space git status --porcelain ?? with space NO QOUTES git add with\ space git status --porcelain A with space - WITH QOUTES git --version git version