From: | Віталій Тимчишин <tivv00(at)gmail(dot)com> |
---|---|
To: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: GIT move |
Date: | 2012-02-08 19:57:09 |
Message-ID: | CABWW-d2jZc3owYes7oXgEe3ma+0kTTqyorqcc2-M3iQbQbqV9Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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: https://github.com/blog/712-pull-requests-2-0 .
> 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:
> http://developer.github.com/v3/pulls/ ), 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.
--
Best regards,
Vitalii Tymchyshyn
From | Date | Subject | |
---|---|---|---|
Next Message | Jonas Sundman | 2012-02-09 07:17:56 | Re: bug on to do list reproducable at version 9.0-801 |
Previous Message | Maciek Sakrejda | 2012-02-08 17:29:11 | Re: GIT move |