Re: Pulling one commit at a time.

From: Sean Estabrooks <seanlkml@sympatico.ca>
Date: Aug 24, 2009, 08:20 UTC
Message-ID: <BLU0-SMTP3926FD52F3B0ED67F486AAAEF90@phx.gbl>
In-Reply-To: <4A92476A.4060205@microchip.com>

On Mon, 24 Aug 2009 13:25:22 +0530 Sanjiv Gupta <sanjiv.gupta@microchip.com> wrote:

Hi Sanjiv,

Show 6 quoted lines

> What I would like is to "test *every* commit" available in the public 
> master. There would be no local changes or commits that aren't pushed in 
> the private copy.
> So I just want to clone one copy from the public master and then just 
> keep pulling commits from the public master one by one and run 
> regressions on each one.

There's no reason to ask for the commits from the public master one by one. You can download them all in one operation. After that it is a local operation to checkout each new commit and build-test it. This is more efficient than needing a network operation to get each commit individually.

As an aside, you might not really need to test each and every commit. It is likely enough to just test the most recent commit since it is built on top of all the commits that came before it. Essentially you'd be testing all the new commits at once and only need to test more commits (git bisect) if you found a regression with that first test.

> It's a damn simple thing in SVN world.

With Git you have a complete local copy of the history. Once you're up to date with remote master you can checkout each new commit at your leisure pretty damn simply ;o)

Cheers, Sean