On Wed, Jun 17, 2020 at 11:30:26AM +0200, Martin Liška wrote:
> On 6/17/20 10:58 AM, Jakub Jelinek wrote:
> > On Wed, Jun 17, 2020 at 10:46:19AM +0200, Martin Liška wrote:
> > > One minor limitation is that the timestamp (commit date)
> > > of the original commit is lost so that's why we print:
> >
emented
by git_repository.py (using GitPython). For server hook we don't need it.
Is the output better now?
Martin
Jakub
>From ccfd5448c3476dab570ecd7facf0a43afc4c1c4d Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Wed, 17 Jun 2020 10:41:17 +0200
Subject: [PATCH] gcc-changelog: S
On Wed, Jun 17, 2020 at 10:46:19AM +0200, Martin Liška wrote:
> One minor limitation is that the timestamp (commit date)
> of the original commit is lost so that's why we print:
Why? You have the
(cherry picked from commit 8cff672cb9a132d3d3158c2edfc9a64b55292b80)
line, so you can
git log -1 --fo
Hey.
Jakub asked me to add 'Backported from master' heading to backports
that were created from git cherry-pick -x.
So it will newly generate:
git gcc-verify e1d68582022cfa2b1dc76646724b397ba2739439 -p
Checking e1d68582022cfa2b1dc76646724b397ba2739439: OK
-- gcc/ChangeLog --
2020-06-12
