Re: [boost] [testing] How do you interpret the SHA1 revision(outdated results)?

Subject: Re: [boost] [testing] How do you interpret the SHA1 revision(outdated results)?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-01-24 07:40:19

On Thu, Jan 23, 2014 at 5:14 PM, Daniel James <dnljms_at_[hidden]> wrote:

> On 23 January 2014 11:57, Daniel James <dnljms_at_[hidden]> wrote:
> >
> > I could possibly improve the commit messages. An easy change would be
> > to include the submodule's branch (not the super-project's since
> > commits can appear on multiple branches), I might try doing that
> > tonight.
>
> OK, I've done that. You can see the new message at:
>
>
> https://github.com/boostorg/boost/commit/f099295d881f8ec551fe9f56086f50a6648331e8
>

Nice! If you want to shorten the SHA to the first six digits, that's plenty
and shortening is a commonplace in the git world.

>
> Let me know if you have any ideas or opinions. I want to include more
> information in the commit (maybe the new submodule commits or maybe
> the dates from the updated submodules), but I don't currently have a
> good way to get information from the submodules themselves, so I can't
> do much at the moment.
>

Timestamp?

I didn't follow the discussion of timestamps closely, so am not sure if a
timestamp could be generated that would be useful, however.

--Beman