# git format-patch glitch?

2 messages from 2009-08-06 to 2009-08-06. Participants: Mark A Rada, Tomas Carnecky.
Thread: https://gitlist.dev/t/20426

## Mark A Rada, 2009-08-06 04:55

Subject: git format-patch glitch?
Message-ID: <ED82D2F5-3E0A-491E-BDD8-3742B769193D@uwaterloo.ca>
URL: https://gitlist.dev/e/ED82D2F5-3E0A-491E-BDD8-3742B769193D%40uwaterloo.ca

```
I noticed this at the top of every patch that git creates for me:

 From 3c34cfa3987c310e4c3194e06d25a08557f0bdb0 Mon Sep 17 00:00:00 2001

Well, the commit hash is different, but the date is always the same.  
Is this expected
behaviour? It happens for different repositories on different  
computers that use different
versions of git.

--
Mark A Rada (ferrous26)
marada@uwaterloo.ca

```

## Tomas Carnecky, 2009-08-06 07:57

Subject: Re: git format-patch glitch?
Message-ID: <2319BD2A-EA70-4C77-940E-924EF833379B@dbservice.com>
URL: https://gitlist.dev/e/2319BD2A-EA70-4C77-940E-924EF833379B%40dbservice.com
In-Reply-To: <ED82D2F5-3E0A-491E-BDD8-3742B769193D@uwaterloo.ca>

```

On Aug 6, 2009, at 6:55 AM, Mark A Rada wrote:

> I noticed this at the top of every patch that git creates for me:
>
> From 3c34cfa3987c310e4c3194e06d25a08557f0bdb0 Mon Sep 17 00:00:00 2001
>
> Well, the commit hash is different, but the date is always the same.  
> Is this expected
> behaviour? It happens for different repositories on different  
> computers that use different
> versions of git.

http://thread.gmane.org/gmane.comp.version-control.git/124082

tom

```
