Michael Paquier writes:
> Ah, thanks. I did not notice this one. Let's leave that alone then,
> except if there are more people in favor of fixing the whole set.
Might be worth running Bruce's copyright-update script again, though
I'd suggest waiting till after the CF
On Tue, Mar 30, 2021 at 11:09:47AM +0800, Julien Rouhaud wrote:
> This is actually gistfuncs.c.
Thanks, you are right. There's typo in the mail title.
Sorry for your confusion.
On Tuesday, March 30, 2021 12:08 PM, Michael Paquier wrote:
>Thanks. If I look at the top of HEAD, it is not the only
On Tue, Mar 30, 2021 at 11:09:47AM +0800, Julien Rouhaud wrote:
> This is actually gistfuncs.c. There are other files impacted
> (jsonbsubs, hex, sha1, pg_iovec and rewriteSearchCycle) see
> https://www.postgresql.org/message-id/20210323143438.gb...@momjian.us.
Ah, thanks. I did not notice this
Hi,
On Tue, Mar 30, 2021 at 10:51 AM tanghy.f...@fujitsu.com
wrote:
>
> Hi
>
> Found one code committed at 2021.01.13 with copyright 2020.
> Fix it in the attached patch.
This is actually gistfuncs.c. There are other files impacted
(jsonbsubs, hex, sha1, pg_iovec and rewriteSearchCycle) see
htt
On Tue, Mar 30, 2021 at 02:51:26AM +, tanghy.f...@fujitsu.com wrote:
> Found one code committed at 2021.01.13 with copyright 2020.
> Fix it in the attached patch.
Thanks. If I look at the top of HEAD, it is not the only place. I am
to blame for some of them like src/common/sha1. Will fix i
Hi
Found one code committed at 2021.01.13 with copyright 2020.
Fix it in the attached patch.
Regards,
Tang
0001-Update-copyright-for-2021.patch
Description: 0001-Update-copyright-for-2021.patch
On Tue, Jan 2, 2018 at 04:49:28PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > I am ready to update the copyright notice on HEAD for 2018. Any
> > objections? This shouldn't affect any pending patches since the
> > copyright text is normally isolated at the top of the file.
>
> Sure, go
Bruce Momjian writes:
> I am ready to update the copyright notice on HEAD for 2018. Any
> objections? This shouldn't affect any pending patches since the
> copyright text is normally isolated at the top of the file.
Sure, go for it.
In the past we've often had to go back and clean up after pat
I am ready to update the copyright notice on HEAD for 2018. Any
objections? This shouldn't affect any pending patches since the
copyright text is normally isolated at the top of the file.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprised
