public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Jelte Fennema-Nio <[email protected]>
To: Euler Taveira <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Opinion poll: Sending an automated email to a thread when it gets added to the commitfest
Date: Thu, 15 Aug 2024 15:33:17 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGECzQRgKtmjxc1E7L4LxvzabaWHE47_bzfw7zxfwGQsYzYvYQ@mail.gmail.com>
References: <CAGECzQSs61oWBtkQDe1V38Q8Z4+-jcM=EtPbM7_uX0jbs7zs6g@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAGECzQRgKtmjxc1E7L4LxvzabaWHE47_bzfw7zxfwGQsYzYvYQ@mail.gmail.com>

On 15.08.24 09:59, Jelte Fennema-Nio wrote:
> I realized a 5th thing that I would want in the email and cf entry page
> 
> 5. A copy-pastable set of git command that checks out the patch by
> downloading it from the cfbot repo like this:
> 
> git config branch.cf/5107.remote
> https://github.com/postgresql-cfbot/postgresql.git
> git config branch.cf/5107.merge refs/heads/cf/5107
> git checkout -b cf/5107
> git pull

Maybe this kind of thing should rather be on the linked-to web page, not 
in every email.

But a more serious concern here is that the patches created by the cfbot 
are not canonical.  There are various heuristics when they get applied. 
I would prefer that people work with the actual patches sent by email, 
at least unless they know exactly what they are doing.  We don't want to 
create parallel worlds of patches that are like 90% similar but not 
really identical.

view thread (19+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Opinion poll: Sending an automated email to a thread when it gets added to the commitfest
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox