Re: rebase -p confusion in 1.6.1

From: Stephan Beyer <s-beyer@gmx.net>
Date: Jan 15, 2009, 15:09 UTC
Message-ID: <20090115150913.GE10045@leksak.fem-net>
In-Reply-To: <slrngmujc4.sf.sitaramc@sitaramc.homelinux.net>

Sitaram Chamarty wrote:

Show 9 quoted lines

> On 2009-01-15, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 
> > I turned this into a proper test case (to show what would be most helpful 
> > if you report bugs like this in the future).
> 
> Thanks.  I'll keep that in mind.
> 
> What is the significance of test_tick?  I can see what it is
> doing, but am trying to understand why.

When you run the test case a second, third, fourth time, the commit times would be all different without test_tick. This is bad for bugfixing when you need to inspect the test case repo a little further. (When the commit times change, the commit ids change, too.) So setting the time and counting it artificially up is nice to get the same SHAs over and over.

Regards,
  Stephan

-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F