From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH 0/5] Several ui-patch.c tweaks and tests!
Date: Mon, 26 Aug 2013 20:38:30 +0200 [thread overview]
Message-ID: <1377542315-19728-1-git-send-email-cgit@cryptocrack.de> (raw)
Adding tests for the new ui-patch.c features. Also contains fixes for
two minor issues I discovered while writing those tests.
Lukas Fleischer (5):
t0108: Avoid unnecessary fork()
ui-patch.c: Fix signature delimiter
ui-patch.c: Add additional newline after each patch
t0108: Compare output with git-format-patch(1)
t0108: Add tests for revision ranges
tests/t0108-patch.sh | 30 +++++++++++++++++++++++++++---
ui-patch.c | 2 +-
2 files changed, 28 insertions(+), 4 deletions(-)
--
1.8.4.rc3.500.gc3113b0
next reply other threads:[~2013-08-26 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 18:38 cgit [this message]
2013-08-26 18:38 ` [PATCH 1/5] t0108: Avoid unnecessary fork() cgit
2013-08-26 18:38 ` [PATCH 2/5] ui-patch.c: Fix signature delimiter cgit
2013-08-26 18:38 ` [PATCH 3/5] ui-patch.c: Add additional newline after each patch cgit
2013-08-26 18:38 ` [PATCH 4/5] t0108: Compare output with git-format-patch(1) cgit
2013-08-26 18:38 ` [PATCH 5/5] t0108: Add tests for revision ranges cgit
2013-08-26 19:05 ` [PATCH 0/5] Several ui-patch.c tweaks and tests! Jason
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=1377542315-19728-1-git-send-email-cgit@cryptocrack.de \
--to=cgit@lists.zx2c4.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).