Hello,
even though the SHA1 commit ID can be looked at, a changing commit ID
doesn't mean changed code. What if you hat two commits since the last
build, one that adds a change and another that reverts it? You are seeing
the same code, yet you rebuild it.
If you don't have a decent build system
my interest is in creating scripts to build software stored in GIT repos.
(I am a build engineer)
Brand new to GIT, actually never used it, but now i have to build it.
I just want to 'get' the latest revision of the source code on a branch (or
master depending on the case), change dir to it,
Also, a free on-line book: https://git-scm.com/book/en/v2
On 02/10/16 18:37, Suu wrote:
Before I build/compile a git branch, I would like to know whether it has
changed since the last time I built it.
If no change, I won't bother to build.
in Subversion, it's a "revision number" that
Your gut is correct. :)
On 02/10/16 18:47, Suu Quan wrote:
Thanks Leam
Follow up.
Case 2: already exists from a previous clone.
Question: is it more efficient to
1.Do what Leam just said: “cd ; git pull”
or
2.Rm –rf
git clone
??
(gut feeling it’s #1 that is more efficient)
Git pull only pulls the changes so it will be much faster than clone the
whole repo all over again
On 11 Feb 2016 06:48, "Suu Quan" wrote:
> Thanks Leam
>
>
>
> Follow up.
>
> Case 2: already exists from a previous clone.
>
>
>
> Question: is it more efficient to
>
> 1. Do
Suu writes:
> Before I build/compile a git branch, I would like to know whether it has
> changed since the last time I built it.
> If no change, I won't bother to build.
>
> in Subversion, it's a "revision number" that identifies the whole set of
> source code at the time. If you commit
Before I build/compile a git branch, I would like to know whether it has
changed since the last time I built it.
If no change, I won't bother to build.
in Subversion, it's a "revision number" that identifies the whole set of
source code at the time. If you commit another set of changes to the
Hmm...depends. Yes, the git hash will be the same if you're on the same
version. How manual do you want it to be? "git status" will show you the
status but isn't manual.
You can "git log | head -1' for the commit hash, if that's what you
want. For example:
git log | head -1
Thanks Leam
Follow up.
Case 2: already exists from a previous clone.
Question: is it more efficient to
1. Do what Leam just said: “cd ; git pull”
or
2. Rm –rf
git clone
??
(gut feeling it’s #1 that is more efficient)
-Original Message-
From: Leam Hall