All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ewa Śliwińska" <kreska07@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Sergey Organov <sorganov@gmail.com>,
	Shourya Shukla <shouryashukla.oo@gmail.com>,
	git@vger.kernel.org
Subject: Re: file is showing as modified even that it was never commited
Date: Tue, 5 May 2020 10:10:58 +0200	[thread overview]
Message-ID: <CAEoQP9jvpCnC0Ag=xZVSpCE_CgyddLooSGi35NcMQf=0se3BEw@mail.gmail.com> (raw)
In-Reply-To: <87zhamiz3r.fsf@igel.home>

We probably don't understand each other. At least I don't get you.

I don't know what you think I want with them, but it's definitely not adding.
And the problem is I would like to know what HAPPENED or why they are
displaying as they were added when at the same time it seems they
weren't (that was never my intention).

On Tue, 5 May 2020 at 10:07, Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Mai 05 2020, Ewa Śliwińska wrote:
>
> > That is not the problem now, I worry only about those "modified" files.
>
> Just git add them again.  Each time you git add a file, only the current
> content is staged.  If you modify it further, you need to git add it
> again if you want to commit the new contents.
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
> "And now for something completely different."

  reply	other threads:[~2020-05-05  8:11 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
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 [this message]
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='CAEoQP9jvpCnC0Ag=xZVSpCE_CgyddLooSGi35NcMQf=0se3BEw@mail.gmail.com' \
    --to=kreska07@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    --cc=shouryashukla.oo@gmail.com \
    --cc=sorganov@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.