The easiest solution is to ask any committers
who pushed changes during that time period to push their changes again.
The commits should still be sitting in their local git clone. This is what
we did in the Orion project, although we first had to ask the webmaster
to disable their hook that verifies author information on the commits:
Markus Tiede <Markus.Tiede@xxxxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
05/31/2011 10:49 AM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [cross-project-issues-dev] git repository
Are there currently any plans on how to resolve /
track this issue? Or
should all projects solve this on their own?
Thanks in advance,
On 05/31/2011 03:45 PM, Dennis Hübner wrote:
> Am 31.05.11 15:38, schrieb Andrew Overholt:
>>> we noticed that our latest commits between 03.05.2011 10:56
>>> 30.05.2011 20:00 are gone.
>> Was the first date a typo or were 27 days of history really missing?
> Yes it's a typo, sorry :)
>> cross-project-issues-dev mailing list
cross-project-issues-dev mailing list