| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Git cvsserver serious issue |
| Date: | 2010-10-07 19:31:22 |
| Message-ID: | 4CAE200A.2060505@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members pgsql-hackers |
On 10/07/2010 10:11 AM, Magnus Hagander wrote:
>
>> OTOH, this patch seems pretty small and simple to maintain.
> True, it is rather small.
>
> Does anybody know if there's an automated way to maintain that on
> freebsd ports, and if so, how that works? I want to be *sure* we can't
> accidentally upgrade git-cvsserver *without* the patch, since that is
> a security issue.
>
Why not just make a local copy somewhere else and patch and run that?
It's just a Perl script, no?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-10-07 19:37:48 | Re: Git cvsserver serious issue |
| Previous Message | Magnus Hagander | 2010-10-07 14:11:00 | Re: Git cvsserver serious issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-10-07 19:35:10 | Re: On Scalability |
| Previous Message | Kevin Grittner | 2010-10-07 19:28:50 | Re: Issues with Quorum Commit |