From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jeremy Huddleston Sequoia <jeremyhu@apple.com>,
Akilsrin <Akilsrin@apple.com>,
Christian Couder <christian@gitlab.com>,
Tim Triemstra <timt@apple.com>, Eliran Mesika <eliran@gitlab.com>
Subject: Re: Subscribing Apple people to git-security@googlegroups.com
Date: Tue, 3 Jul 2018 08:48:14 -0700 [thread overview]
Message-ID: <20180703154814.GA51821@aiede.svl.corp.google.com> (raw)
In-Reply-To: <20180703133645.GA20316@sigill.intra.peff.net>
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 Mon, Jul 02, 2018 at 01:15:19PM -0700, Jeremy Huddleston Sequoia wrote:
>> I'm very very interested in having reduced differences between what we
>> ship in Xcode and what is upstream.
[...]
> Thanks for sharing. Skimming over it, I see:
>
> - several of the changes look related to run-time relocation. There was
> a series that shipped in v2.18.0 related to this, so that may reduce
> your diff once you rebase.
>
> - The xcode_gitattributes() bits aren't likely to go upstream as-is.
> But possibly these could ship as a default $sysconfdir/gitattributes?
>
> - the rest look like assorted little fixes that probably could go
> upstream
I agree with Peff's assessment. I'd also like to emphasize that
upstream is happy to see an [FYI/PATCH] when you have a divergence,
which would provide a thread to reply to to figure out whether there's
some generalization that is suitable for upstream. (For example,
maybe we want some Makefile knob to allow setting some baked-in
attributes.)
Thanks,
Jonathan
next prev parent 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 ` Subscribing Apple people to git-security@googlegroups.com Jeff King
[not found] ` <91A9F3A0-5F3F-4137-9A40-CB42EDE4F243@apple.com>
[not found] ` <9AE01C9B-7D10-45F2-8910-1607A19DF722@apple.com>
2018-07-02 21:17 ` Jeff King
2018-07-03 13:36 ` Jeff King
2018-07-03 15:48 ` Jonathan Nieder [this message]
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=20180703154814.GA51821@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=Akilsrin@apple.com \
--cc=christian@gitlab.com \
--cc=eliran@gitlab.com \
--cc=jeremyhu@apple.com \
--cc=peff@peff.net \
--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).