From: "Nathan W. Panike" <nathan.panike@gmail.com>
To: git@vger.kernel.org
Cc: "Nathan W. Panike" <nathan.panike@gmail.com>
Subject: [PATCH v2] Allow format-patch to create patches for merges
Date: Mon, 26 Jan 2009 10:43:32 -0600 [thread overview]
Message-ID: <1232988212-8613-1-git-send-email-nathan.panike@gmail.com> (raw)
In-Reply-To: <d77df1110901260827j2200fe41oe1b84c387d88aba () mail ! gmail ! com>
The behavior for git format-patch is to ignore merge commits, producing an
empty patch. The code does not allow the user to change this behavior. This
patch changes that behavior by allowing the user to specify -c or -m at the
command line to produce a patch for a merge commit.
Signed-off-by: Nathan W. Panike <nathan.panike@gmail.com>
---
Add Sign off.
This seems to solve my problem, but maybe my workflow is sufficiently different
that it is a problem no one else has. Maybe someone can point me in a direction
that solves problems more users have.
Thanks,
Nathan Panike
builtin-log.c | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/builtin-log.c b/builtin-log.c
index 2ae39af..ea4729d 100644
--- a/builtin-log.c
+++ b/builtin-log.c
@@ -994,10 +994,6 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
continue;
}
- /* ignore merges */
- if (commit->parents && commit->parents->next)
- continue;
-
if (ignore_if_in_upstream &&
has_commit_patch_id(commit, &ids))
continue;
--
1.6.1.1.GIT
next parent reply other threads:[~2009-01-26 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d77df1110901260827j2200fe41oe1b84c387d88aba () mail ! gmail ! com>
2009-01-26 16:43 ` Nathan W. Panike [this message]
2009-01-26 19:34 ` [PATCH v2] Allow format-patch to create patches for merges Sverre Rabbelier
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=1232988212-8613-1-git-send-email-nathan.panike@gmail.com \
--to=nathan.panike@gmail.com \
--cc=git@vger.kernel.org \
/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).