All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Andy Falanga \(afalanga\)" <afalanga@micron.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's happening to the index
Date: Wed, 29 Jun 2016 09:43:17 +0200	[thread overview]
Message-ID: <vpqoa6kh23u.fsf@anie.imag.fr> (raw)
In-Reply-To: <5772FF0E.6030503@micron.com> (Andy Falanga's message of "Tue, 28 Jun 2016 22:49:51 +0000")

"Andy Falanga (afalanga)" <afalanga@micron.com> writes:

> The strange thing now is, after the script exits, I then call "git 
> fetch" in the recipe.  I can see from the output of make that the remote 
> db is fetched.  However, when I call "git show 
> origin/rpm:path/to/rpm_build_num" from the makefile I get the *previous* 
> number.  Yet, as soon as the make process exits, I call "git show 
> origin/rpm:path/to/rpm_build_num" and it shows the correct number!

My bet would be that you are running the commands in two different
repositories. Try running

  pwd && git show origin/rpm:path/to/rpm_build_num

In the Makefile and after make completes, and check that pwd returns the
same thing. Also, to avoid getting the issue you previously had, try

  cd $(pwd) && pwd && git show origin/rpm:path/to/rpm_build_num

too.

> Is there some sort of strange file caching that happening
> when make starts that, although the local db is updated, I don't get
> what I'm after?

Git can keep information either in RAM, hence not shared between git
invocations (so running git within or outside the Makefile wouldn't
matter), or on disk, but then inside or outside the Makefile doesn't
matter either.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2016-06-29  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 14:30 What's happening to the index Andy Falanga (afalanga)
2016-06-28 15:17 ` Matthieu Moy
2016-06-28 22:49   ` Andy Falanga (afalanga)
2016-06-29  7:43     ` Matthieu Moy [this message]
2016-07-03  8:21     ` David

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=vpqoa6kh23u.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=afalanga@micron.com \
    --cc=git@vger.kernel.org \
    /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.