Re: Use stack-allocated StringInfoData
| От | David Rowley | 
|---|---|
| Тема | Re: Use stack-allocated StringInfoData | 
| Дата | |
| Msg-id | CAApHDvpTAnwFWxJ3NR3Xx6gqY_iaV+YsCY7=41oJJ3h-urGESQ@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Re: Use stack-allocated StringInfoData (Mats Kindahl <mats.kindahl@gmail.com>) | 
| Ответы | 
                	
            		Re: Use stack-allocated StringInfoData
            		
            		 | 
		
| Список | pgsql-hackers | 
On Tue, 4 Nov 2025 at 09:20, Mats Kindahl <mats.kindahl@gmail.com> wrote: > This is using Coccinelle to transform the text based on a semantic patch (which is included in the patch). Unfortunatelyit mess with the whitespace a bit so it is necessary to run pg_intent after. I'm surprised that there are whitespacechanges that should not be there, but I'll take a look. pgindent likely won't put back the types of changes that were made here. I think you're going to have to manually review anything that comes out of any automated tool, at least certainly until there's some confidence that the scripts are configured correctly. Loading extra work onto reviewers or committers that you could have easily done yourself isn't really a sustainable thing. We just lack bandwidth for that, plus it's bad etiquette. A few tips: It's fine to post rough patches to demonstrate ideas to the list, but make that clear when doing so. If your intention is that what you're sending gets committed, then please aim for as high a quality as you can. There just won't be any long-term patience for series of unvetted-by-human transformation patches from tools such as Coccinelle around here, especially so if you expect the community to vet them for you. I'm not saying that's what you're doing, but if you are, please take this advice. David
В списке pgsql-hackers по дате отправления: