git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: [PATCH 0/6] miscellaneous patches
Date: Sun, 06 Oct 2013 21:47:34 +0100	[thread overview]
Message-ID: <5251CC66.30004@ramsay1.demon.co.uk> (raw)


Hi Jonathan,

These patches don't have too much in common, hence the subject
line, except perhaps that 4 of them fix sparse warnings.

Note that the fourth patch is actually a simplified version of
an earlier RFC patch. Junio didn't like the idea of using a
build variable (GIT_TEST_HIGHLIGHT_BIN) to set the path to the
'correct' highlight tool. see:
http://article.gmane.org/gmane.comp.version-control.git/234138

Having recently had to re-configure Thunderbird, I noticed that
the documentation needed updating. (actually, I was sure that I
had sent a similar patch, years ago, when I last did this! :-P )

ATB,
Ramsay Jones

Ramsay Jones (6):
  config.c: Fix a sparse warning
  refs.c: Fix a sparse warning
  wrapper.c: Fix a sparse warning
  t9500-*.sh: Fix highlight test hang on Linux Mint
  git-format-patch.txt: Add to Thunderbird configuration
  sparse: Fix some "using sizeof on a function" warnings

 Documentation/git-format-patch.txt     | 3 ++-
 Makefile                               | 3 +++
 config.c                               | 2 +-
 refs.c                                 | 2 +-
 t/t9500-gitweb-standalone-no-errors.sh | 6 ++++--
 wrapper.c                              | 2 ++
 6 files changed, 13 insertions(+), 5 deletions(-)

-- 
1.8.4

             reply	other threads:[~2013-10-06 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 20:47 Ramsay Jones [this message]
2013-10-14 23:25 ` [PATCH 0/6] miscellaneous patches Jonathan Nieder
2013-10-15 14:41   ` Ramsay Jones

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=5251CC66.30004@ramsay1.demon.co.uk \
    --to=ramsay@ramsay1.demon.co.uk \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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.
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).