Doug,
> > --- save as .git/hooks/sendemail-validate ---
> > #!/bin/sh
> >
> > set -e
> >
> > changeid=$(sed 's/^Change-Id: \(I.*\)$/\1/;t;d' $1)
> > date=$(date +%s)
> > sed 's/^Change-Id: I.*$//;T;d' -i $1
> > sed "s/^From: /Message-Id: <$date-$changeid@changeid>\nFrom: /" -i $1
> > #--- end
Hi,
On Thu, Sep 26, 2019 at 6:50 PM Simon Glass wrote:
>
> Hi Doug,
>
> On Tue, 3 Sep 2019 at 13:15, Douglas Anderson wrote:
> >
> > As per the centithread on ksummit-discuss [1], there are folks who
> > feel that if a Change-Id is present in a developer's local commit that
> > said Change-Id
Hi Doug,
On Tue, 3 Sep 2019 at 13:15, Douglas Anderson wrote:
>
> As per the centithread on ksummit-discuss [1], there are folks who
> feel that if a Change-Id is present in a developer's local commit that
> said Change-Id could be interesting to include in upstream posts.
> Specifically if two
Hi Doug,
> > Actually, the important part for me is to be to be able to have change-
> > ids locally (e.g. for working with gerrit), and not have that leak out
> > to the community (that doesn't like them).
> >
> > As a maintainer in the community, I'll also need to change the
> >
Johannes,
On Thu, Sep 5, 2019 at 12:48 PM Johannes Berg wrote:
>
> On Tue, 2019-09-03 at 13:15 -0700, Douglas Anderson wrote:
> >
> > Let's give that a try.
> >
> > In theory (if there is enough adoption) this could help a tool more
> > reliably find various versions of a commit.
>
> It's not
On Tue, 3 Sep 2019 at 14:15, Douglas Anderson wrote:
>
> As per the centithread on ksummit-discuss [1], there are folks who
> feel that if a Change-Id is present in a developer's local commit that
> said Change-Id could be interesting to include in upstream posts.
> Specifically if two commits
On Thu, 2019-09-05 at 21:48 +0200, Johannes Berg wrote:
>
> As a maintainer in the community, I'll also need to change the
> .git/hooks/commit-msg script that comes with gerrit to not add a Change-
> Id if the commit comes with a Link: tag already, but that should be
> easy.
This, I should
On Tue, 2019-09-03 at 13:15 -0700, Douglas Anderson wrote:
>
> Let's give that a try.
>
> In theory (if there is enough adoption) this could help a tool more
> reliably find various versions of a commit.
It's not quite as good as this (yet), but a very simple version of it
for git-send-email
As per the centithread on ksummit-discuss [1], there are folks who
feel that if a Change-Id is present in a developer's local commit that
said Change-Id could be interesting to include in upstream posts.
Specifically if two commits are posted with the same Change-Id there's
a reasonable chance
9 matches
Mail list logo
