Re: bugs and bug tracking
| От | Magnus Hagander |
|---|---|
| Тема | Re: bugs and bug tracking |
| Дата | |
| Msg-id | CABUevEzmadsC_kaOE2=fn0W7=yVt+-Chzgdx-WN2L4Rw5nRcMg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: bugs and bug tracking (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Список | pgsql-hackers |
On Wed, Oct 7, 2015 at 8:47 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Nathan Wagner wrote:
> I am still working out exactly how to find multiple matching commits
> along different branches. I'm running git patch-id on every commit,
> but that will take a while.
See src/tools/git_changelog (both the output and the implementation).
Isn't that rather what you want? patch-id will give different answers
for patches that required conflict fixing.
> How often are the bugs mail list archives updated? I've got a bunch of
> posts to the bugs list in my inbox that aren't in the archive download.
As each message is received. What posts do you see that are not in the
archive?
I'm pretty sure Nathan is talking about the publically available mbox files, which are updated by rsync on a schedule. I don't recall exactly how often.
However - Nathan, I'd suggest you don't focus too hard on that. As I said before if we go somewhere with this in the end, it should use the APIs to get the data, in which case they will be instant as Alvaro says. Some delay during testing should not be a problem, I hope.
В списке pgsql-hackers по дате отправления: