git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Christian Couder <christian@gitlab.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Jeremy Huddleston Sequoia <jeremyhu@apple.com>,
	Tim Triemstra <timt@apple.com>, Eliran Mesika <eliran@gitlab.com>
Subject: Re: Subscribing Apple people to git-security@googlegroups.com
Date: Mon, 2 Jul 2018 15:50:17 -0400	[thread overview]
Message-ID: <20180702195016.GA17102@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGba+=U4nbxL2uuSxyqyZqiiavJpo_E=GhUkipz6DczLdmnkgQ@mail.gmail.com>

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 on this.

Unfortunately I don't think this will quite solve the issue we had, just
because people get their copy of Git in various ways. So Homebrew
updated pretty promptly, but people going to git-scm.com to find a
binary package were left without help. Likewise, this will help people
getting Git as part of XCode, but not people gettin the package from
git-scm.com.

All that said, I'm happy to get as many binary packagers into the loop
as early as possible. It can only help, even if it doesn't solve all
problems. :)

> Please add these addresses to the git-security mailing list:
>     jeremyhu@apple.com
>     akilsrin@apple.com
>     dt-epm@group.apple.com

Done.

> Please add these GitHub accounts to the cabal repo:
>     jeremyhu

Done.

>     productsecurityOSSapple

I couldn't find that account. Is it maybe a team name within the apple
org or something?

> I am also personally very happy with the Apple developers' willingness
> to get involved and help.

Yes, welcome aboard!

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
things that could probably be considered upstream.

-Peff

       reply	other threads:[~2018-07-09 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGba+=U4nbxL2uuSxyqyZqiiavJpo_E=GhUkipz6DczLdmnkgQ@mail.gmail.com>
2018-07-02 19:50 ` Jeff King [this message]
     [not found]   ` <91A9F3A0-5F3F-4137-9A40-CB42EDE4F243@apple.com>
     [not found]     ` <9AE01C9B-7D10-45F2-8910-1607A19DF722@apple.com>
2018-07-02 21:17       ` Subscribing Apple people to git-security@googlegroups.com Jeff King
2018-07-03 13:36     ` Jeff King
2018-07-03 15:48       ` Jonathan Nieder
2018-07-03 16:01         ` Jeff King
2018-07-09 22:48           ` Jonathan Nieder
2018-07-10 12:27       ` Ævar Arnfjörð Bjarmason
2018-07-10 18:54         ` Jeremy Huddleston Sequoia
2018-07-10 13:24   ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180702195016.GA17102@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian@gitlab.com \
    --cc=eliran@gitlab.com \
    --cc=jeremyhu@apple.com \
    --cc=jrnieder@gmail.com \
    --cc=timt@apple.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).