From: Thiago Farina <tfransosi@gmail.com>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: git@vger.kernel.org
Subject: Re: Tracking remote branches
Date: Mon, 14 Sep 2009 15:30:10 -0300 [thread overview]
Message-ID: <a4c8a6d00909141130o628a069fu4c489b25f95f543d@mail.gmail.com> (raw)
In-Reply-To: <20090914050145.GA12985@vidovic>
On Mon, Sep 14, 2009 at 2:01 AM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> wrote:
> The 13/09/09, Thiago Farina wrote:
>> Hi,
>>
>> I know that I could do simply, instead of above:
>> $ git checkout --track -b maint origin/maint
>
> Or
> $ git checkout -t origin/maint
>
>> OK, now I switched to maint branch. And then I did:
>> $ git status
>>
>> # On branch maint
>> # Changes to be committed
>> # (use "git reset HEAD <file>..." to unstage)
>> #
>> # new file: git-remote-curl
>> # new file: git-replace
>> #
>>
>> What happened here? What I have to do now?
>
> You've probably added these files to the index, mistakenly. If you don't
> have uncommited changes, try :
>
> git checkout -f master
> git branch -D maint
> git checkout -t origin/maint
> git status
>
> The files should now be shown as "Untracked files".
Yeah, now the files has this status. But I don't have anything related
with these files, I didn't add these files.
Why these files has this status? Is supposed to me to do something
about that when this situation occurs?
next prev parent reply other threads:[~2009-09-14 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 0:37 Tracking remote branches Thiago Farina
2009-09-14 5:01 ` Nicolas Sebrecht
2009-09-14 18:30 ` Thiago Farina [this message]
2009-09-14 19:19 ` Heiko Voigt
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=a4c8a6d00909141130o628a069fu4c489b25f95f543d@mail.gmail.com \
--to=tfransosi@gmail.com \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).