Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-10 Thread Jeremy Huddleston Sequoia
> On Jul 10, 2018, at 5:27 AM, Ævar Arnfjörð Bjarmason wrote: > > On Tue, Jul 3, 2018 at 3:36 PM, Jeff King wrote: >> On Mon, Jul 02, 2018 at 01:15:19PM -0700, Jeremy Huddleston Sequoia wrote: >> I hope that maybe they're also interested in reducing the overall diff between

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-10 Thread Johannes Schindelin
Hi Peff, On Mon, 2 Jul 2018, Jeff King wrote: > On Mon, Jul 02, 2018 at 09:29:41PM +0200, Christian Couder wrote: > > > When people complained a month ago about the MacOS package on > > https://git-scm.com/ not being up-to-date after the Git security > > release, I got in touch with Apple

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-10 Thread Ævar Arnfjörð Bjarmason
On Tue, Jul 3, 2018 at 3:36 PM, Jeff King wrote: > On Mon, Jul 02, 2018 at 01:15:19PM -0700, Jeremy Huddleston Sequoia wrote: > >> > I hope that maybe they're also interested in reducing the overall >> > diff between upstream Git and what ships with XCode. Last time I >> > looked (which was

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jonathan Nieder
+git@vger Jeff King wrote: > On Tue, Jul 03, 2018 at 08:48:14AM -0700, Jonathan Nieder wrote: >> Administrivia: do you mind if I bounce these messages to some archived >> list, either git@vger.kernel.org or git-security? Or if we'd prefer >> to avoid the noise from that, do you mind if I work

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jeff King
On Tue, Jul 03, 2018 at 08:48:14AM -0700, Jonathan Nieder wrote: > Administrivia: do you mind if I bounce these messages to some archived > list, either git@vger.kernel.org or git-security? Or if we'd prefer > to avoid the noise from that, do you mind if I work with Eric Wong to > get them

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jeff King
On Mon, Jul 02, 2018 at 01:58:21PM -0700, Akilsrin wrote: > Could “ProdsecOSS " also be added to the > git-security mailing list. It’s another account I control to ensure my > team and I track open source bugs. > > The git repo: could you add https://github.com/product-security-OSS >

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jonathan Nieder
Administrivia: do you mind if I bounce these messages to some archived list, either git@vger.kernel.org or git-security? Or if we'd prefer to avoid the noise from that, do you mind if I work with Eric Wong to get them injected in the https://public-inbox.org/ archive? Hi, Jeff King wrote: > On

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jeff King
On Mon, Jul 02, 2018 at 09:29:41PM +0200, Christian Couder wrote: > When people complained a month ago about the MacOS package on > https://git-scm.com/ not being up-to-date after the Git security > release, I got in touch with Apple people GitLab has been working with > to see if they could help

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jeff King
On Mon, Jul 02, 2018 at 01:15:19PM -0700, Jeremy Huddleston Sequoia wrote: > > I hope that maybe they're also interested in reducing the overall > > diff between upstream Git and what ships with XCode. Last time I > > looked (which was admittedly a while ago), a lot of the changes > > seemed like

Re: Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Jeremy Huddleston Sequoia
+Akila Hi, Replies inline. > On Jul 2, 2018, at 12:50, Jeff King wrote: > > On Mon, Jul 02, 2018 at 09:29:41PM +0200, Christian Couder wrote: > >> When people complained a month ago about the MacOS package on >> https://git-scm.com/ not being up-to-date after the Git security >> release, I

Subscribing Apple people to git-secur...@googlegroups.com

2018-07-09 Thread Christian Couder
Hi Peff (and Jonathan), When people complained a month ago about the MacOS package on https://git-scm.com/ not being up-to-date after the Git security release, I got in touch with Apple people GitLab has been working with to see if they could help on this. As the urgent issue was resolved when