From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: git <git@vger.kernel.org>
Subject: git-format-patch builtin isn't using git-cherry?
Date: Fri, 23 Jun 2006 12:32:01 +1200 [thread overview]
Message-ID: <46a038f90606221732k6d93bcceic2761081d7a7c72b@mail.gmail.com> (raw)
I used to rely on git-format-patch to be calling git-cherry in the bg,
so that I'd know that the obviously merged patches were upstream
alredy. It doesn't seem to do it any more.
Reading cmd_format_patch() in builtin-log.c, it seems to have lost
that magic that made it so useful... :( Can a kind soul that speaks C
fluently help me out here?
(The new format-patch gives me 180 patches to merge/rebase, where the
old one tells me there's only 51. guess which one I prefer ;-) )
cheers,
m
next reply other threads:[~2006-06-23 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 0:32 Martin Langhoff [this message]
2006-06-23 12:05 ` git-format-patch builtin isn't using git-cherry? Johannes Schindelin
2006-06-23 12:23 ` Timo Hirvonen
2006-06-23 12:33 ` Johannes Schindelin
2006-06-23 15:44 ` [FYI/PATCH] diff: add diff_flush_patch_id() Johannes Schindelin
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=46a038f90606221732k6d93bcceic2761081d7a7c72b@mail.gmail.com \
--to=martin.langhoff@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).