All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: "Ewa Śliwińska" <kreska07@gmail.com>
Cc: Shourya Shukla <shouryashukla.oo@gmail.com>, git@vger.kernel.org
Subject: Re: file is showing as modified even that it was never commited
Date: Mon, 04 May 2020 20:17:20 +0300	[thread overview]
Message-ID: <874ksvei1r.fsf@osv.gnss.ru> (raw)
In-Reply-To: CAEoQP9gs-a1NanNpYiFQgTs0C+CeYhbD8rMjoFVat1ZSijNA2A@mail.gmail.com

Dear Ewa,

Please see below.

Ewa Śliwińska <kreska07@gmail.com> writes:

>> That actually was a solution to your problem, not a workaround.

> Not really, because I would like to investigate what happened, not
> just fix it. In that case I could as well recreate repository I
> guess...
>
> I agree that I could add those files accidentally. But I'm really
> disappointed in fact that you seem to ignore all the part where I
> described in details how I checked this and why I think this is not
> the case.

Except you didn't give actual details. Please give exact commands you
issued and exact answers you've got.

For example:

$ ls .test
a  x
$ git status
On branch v4.0
Your branch and 'origin/v4.0' have diverged,
and have 2 and 29 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .test/a

no changes added to commit (use "git add" and/or "git commit -a")
$ git log -- .test
commit e1e7818f4120b5ebc622c8dbf1b257ea8a03530c
Author: Sergey Organov <sorganov@gmail.com>
Date:   Mon May 4 18:55:58 2020 +0300

    Test

$ git log -- .test/a
commit e1e7818f4120b5ebc622c8dbf1b257ea8a03530c
Author: Sergey Organov <sorganov@gmail.com>
Date:   Mon May 4 18:55:58 2020 +0300

    Test
$ git log -- .test/x
$ 

> Could you please answer if there was something wrong with my checking?

Nobody could tell unless you actually show us your checkings.

> I'm asking second time.

Thanks, we've noticed.

-- Sergey

  reply	other threads:[~2020-05-04 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEoQP9gVur=UDDPzHnLq-AryDnd45uYdEs3kajzLrtr572e_rA@mail.gmail.com>
2020-05-03 20:03 ` file is showing as modified even that it was never commited Ewa Śliwińska
2020-05-04  5:55   ` Shourya Shukla
2020-05-04  8:17     ` Ewa Śliwińska
     [not found]     ` <CAEoQP9hyMi=oj18atTJo+dR3ve_zzrLQoOja0CKAAVHei6rA0g@mail.gmail.com>
2020-05-04 12:00       ` Shourya Shukla
2020-05-04 12:11         ` Ewa Śliwińska
2020-05-04 17:17           ` Sergey Organov [this message]
2020-05-04 18:39             ` Ewa Śliwińska
2020-05-04 19:51               ` Sergey Organov
2020-05-04 20:04                 ` Ewa Śliwińska
2020-05-04 20:41               ` Andreas Schwab
2020-05-05  7:49                 ` Ewa Śliwińska
2020-05-05  8:07                   ` Andreas Schwab
2020-05-05  8:10                     ` Ewa Śliwińska
2020-05-05  8:14                       ` Andreas Schwab
2020-05-05  8:19                         ` Ewa Śliwińska
2020-05-05  8:25                           ` Andreas Schwab
2020-05-05  8:34                             ` Ewa Śliwińska

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ksvei1r.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kreska07@gmail.com \
    --cc=shouryashukla.oo@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.