Skip site navigation (1) Skip section navigation (2)

Re: GIT move

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Віталій Тимчишин <tivv00(at)gmail(dot)com>
Cc: Maciek Sakrejda <msakrejda(at)truviso(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: GIT move
Date: 2012-02-10 11:35:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
2012/2/8 Віталій Тимчишин <tivv00(at)gmail(dot)com>:
> 2012/2/8 Maciek Sakrejda <msakrejda(at)truviso(dot)com>
>> > How does a github pull request establish "evidence of intent" ? Please
>> > keep in mind this question is out of ignorance as I am not that
>> > familiar with github.
>> They're pretty nifty: .
>> Although if a record of attribution is a serious concern, having these
>> under github's control is less than ideal. If this is the main
>> concern, perhaps there's a formal way for the project to archive
>> github pull requests (maybe the github API:
>> ), but that's extra work and
>> somewhat more nebulous (as evidence) than a straight mailing list
>> archive.
> That's why I propose for github to send notifications to this list. This can
> be simply configurable and will be more or less much like before.

OK, I see the first pull request came to my gmail address. What has to
be done to get it to the list ?

I imagine we need to add the list as a user to the project ? Getting
github as a subscribed user to the list will be more difficult, but
manageable ?

Can someone elucidate the steps to get pull requests going to the list ?

Also it seems that post-receive hooks are designed to push data to a
website as opposed to simply emailing ??? Is there an easy way to get
email notifications ?


In response to

  • Re: GIT move at 2012-02-08 19:57:09 from Віталій Тимчишин


  • Re: GIT move at 2012-02-10 11:54:57 from Vitalii Tymchyshyn

pgsql-jdbc by date

Next:From: Vitalii TymchyshynDate: 2012-02-10 11:54:57
Subject: Re: GIT move
Previous:From: Kris JurkaDate: 2012-02-10 09:09:11
Subject: Re: Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group