From: "Andy Falanga (afalanga)" <afalanga@micron.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: What's happening to the index
Date: Tue, 28 Jun 2016 14:30:47 +0000 [thread overview]
Message-ID: <57728A17.3010207@micron.com> (raw)
Hi,
I'm using git version 1.8.3.1. I have a process for building RPMs in my
repository. The RPMs are versioned using a "build number". In order to
maintain uniqueness for this build number, I have stored this number to
a file which exists on only a unique branch.
The build process, for an actual release, is intended to be done by
branching on a tag. During that process, a BASH script is called with
checks out "rpm", fetches the repo from remote, merges with origin/rpm,
increments the number and pushes back to origin. It then returns the
branch to the original branch in which the script was called. The make
recipe looks like this:
release:
make clean
cd ../.. && ../tools/increlnum && cd -
if [[ $(TAG) = ......... ]]; then \
git checkout -b rpm_build_$(TAG) $(TAG); \
fi
make rpm RPM_BUILD_NUM=$(shell git show rpm:./rpm_build_num)
After the line calling increlnum is executed, I often have issues with
make unable to spawn the next command because it can't read the current
directory info. Make stops with errors and I'm done. I have the branch
name displayed in my PS1 prompt. I've noticed that, when make errors at
this point, the branch isn't displayed. It's as if the index has become
unstable (or something similar). If I do: cd .. && cd -; all is well.
What is the problem (I'd really like to understand) and what might I do
to correct it?
Andy
next reply other threads:[~2016-06-28 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:30 Andy Falanga (afalanga) [this message]
2016-06-28 15:17 ` What's happening to the index Matthieu Moy
2016-06-28 22:49 ` Andy Falanga (afalanga)
2016-06-29 7:43 ` Matthieu Moy
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=57728A17.3010207@micron.com \
--to=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.