kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Gautam Bhat <mindentropy@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Git pull and untracked files
Date: Sun, 5 Jul 2020 20:38:37 +0530	[thread overview]
Message-ID: <CAM2a4uxiW8rkwbCu=C3OL48inc+BANeB8Exsi4WKK34SPwFhHA@mail.gmail.com> (raw)
In-Reply-To: <225624.1593389726@turing-police>

Thanks! That is helpful.

-Gautam.

On Mon, Jun 29, 2020 at 5:45 AM Valdis Klētnieks
<valdis.kletnieks@vt.edu> wrote:
>
> On Mon, 29 Jun 2020 00:00:23 +0530, Gautam Bhat said:
> > Hi,
> >
> > When I do a git pull to get the latest changes (from v5.2) , git
> > status shows the following files as untracked:
> >
> > scripts/conmakehash
> > scripts/pnmtologo
> > scripts/sortextable
> >
> > I don't see the files in .gitignore too but in the earlier version
> > i.e. v5.2 it is present. These files are binaries, should I go ahead
> > and delete them?
>
> And to add to my reply:  How to figure this out for yourself since
> you already have a git tree...
>
> For the first two, I did a 'git grep conmakehash', which told me it was
> in a different Makefile.  'git blame drivers/tty/vt/Makefile | grep conmakehash'
> popped out the commit for 'git show'...
>
> The last one I had to resort to 'git log | grep -B30 sortextable | more'

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-07-05 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 18:30 Git pull and untracked files Gautam Bhat
2020-06-29  0:02 ` Valdis Klētnieks
2020-06-29  0:15 ` Valdis Klētnieks
2020-07-05 15:08   ` Gautam Bhat [this message]

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='CAM2a4uxiW8rkwbCu=C3OL48inc+BANeB8Exsi4WKK34SPwFhHA@mail.gmail.com' \
    --to=mindentropy@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    /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).