From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH v4 0/4] `git format-patch --stdout id2..id`
Date: Tue, 20 Aug 2013 18:56:11 +0200 [thread overview]
Message-ID: <1377017775-29848-1-git-send-email-cgit@cryptocrack.de> (raw)
Fixed patch generation for root diffs.
Generate proper file names when specifying two revisions.
Lukas Fleischer (4):
ui-diff: Check the return value of get_sha1()
ui-patch.c: Use log_tree_commit() to generate diffs
Allow for creating patch series
ui-patch: Rename variables
cmd.c | 2 +-
ui-diff.c | 23 +++++++----------
ui-patch.c | 87 ++++++++++++++++++++++++++++++++++++++------------------------
ui-patch.h | 3 ++-
4 files changed, 65 insertions(+), 50 deletions(-)
--
1.8.4.rc3.500.gc3113b0
next reply other threads:[~2013-08-20 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 16:56 cgit [this message]
2013-08-20 16:56 ` [PATCH v4 1/4] ui-diff: Check the return value of get_sha1() cgit
2013-08-20 16:56 ` [PATCH v4 2/4] ui-patch.c: Use log_tree_commit() to generate diffs cgit
2013-08-20 16:56 ` [PATCH v4 3/4] Allow for creating patch series cgit
2013-08-20 16:56 ` [PATCH v4 4/4] ui-patch: Rename variables cgit
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=1377017775-29848-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).