From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] compat/regex/regexec.c: Fix some sparse warnings
Date: Wed, 18 May 2011 00:52:40 +0200 [thread overview]
Message-ID: <BANLkTimQ9N3kYP+fWj+ifnav67fBYo1-oA@mail.gmail.com> (raw)
In-Reply-To: <4DD2B304.90305@ramsay1.demon.co.uk>
On Tue, May 17, 2011 at 19:40, Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
> In particular, sparse issues the following warnings:
Aside from this specific change, I think it's a problem that we pull
in external libraries, then apply patches to them that upstream would
probably want, don't tell upstream, and will inevitably have to deal
with conflict when we merge in new versions from upstream.
Maybe we should have some file with contact details for these compat
libraries, and try to resolve issues with upstream if we need to apply
patches like this one?
next prev parent reply other threads:[~2011-05-17 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 17:40 [PATCH] compat/regex/regexec.c: Fix some sparse warnings Ramsay Jones
2011-05-17 22:52 ` Ævar Arnfjörð Bjarmason [this message]
2011-05-18 4:04 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimQ9N3kYP+fWj+ifnav67fBYo1-oA@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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.
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 NNTP newsgroup(s).