list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Ramsay Jones <>
To: Junio C Hamano <>
Cc:, GIT Mailing-list <>
Subject: [PATCH 0/2] sparse warning on next branch
Date: Fri, 2 Mar 2018 02:52:27 +0000	[thread overview]
Message-ID: <> (raw)

Tonight's build had a sparse warning and an additional ./
symbol appear on the 'next' branch. As you know, I like to catch these
on the 'pu' branch before they graduate to 'next', but it seems that I
missed these! :( (The 'pu' branch is quite noisy with regard to sparse
and at the moment).

These patches were developed on top of 'next', however, I also tested
them on top of commit fcfba37337 directly. (Note, this is branch
'ps/contains-id-error-message' merged at commit 9623d6817b).

Ramsay Jones (2):
  ref-filter: mark a file-local symbol as static
  parse-options: remove the unused parse_opt_commits() function

 parse-options-cb.c | 16 ----------------
 parse-options.h    |  1 -
 ref-filter.c       |  2 +-
 3 files changed, 1 insertion(+), 18 deletions(-)


                 reply	other threads:[~2018-03-02  2:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

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

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH 0/2] sparse warning on next branch' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).