From: Ramsay Jones <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: email@example.com, GIT Mailing-list <firstname.lastname@example.org> Subject: [PATCH 0/2] sparse warning on next branch Date: Fri, 2 Mar 2018 02:52:27 +0000 [thread overview] Message-ID: <email@example.com> (raw) Tonight's build had a sparse warning and an additional ./static-check.pl 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 static-check.pl 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(-) -- 2.16.0
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: 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/2] sparse warning on next branch' \ /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
Code repositories for project(s) associated with this 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).