From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] Omit patches that have already been merged from format-patch output.
Date: Mon, 12 Sep 2005 09:08:45 +1200 [thread overview]
Message-ID: <46a038f90509111408f9479e2@mail.gmail.com> (raw)
In-Reply-To: <7voe6zqr9y.fsf@assigned-by-dhcp.cox.net>
> git-cherry). One thing I am reluctant about this is it breaks the
> exact example Johannes just posted.
Well, Johannes example didn't work at all for me. Output was empty,
when I was expecting 4~6 entries.
cheers,
martin
next prev parent reply other threads:[~2005-09-11 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 8:52 git-rev-list and git-format-patch script oddness Martin Langhoff
2005-09-11 9:20 ` Johannes Schindelin
2005-09-11 20:32 ` [PATCH] Omit patches that have already been merged from format-patch output Junio C Hamano
2005-09-11 21:08 ` Martin Langhoff [this message]
2005-09-11 21:10 ` Martin Langhoff
2005-09-12 7:24 ` Martin Langhoff
2005-09-12 9:34 ` Martin Langhoff
2005-09-12 11:48 ` Junio C Hamano
2005-09-12 12:03 ` Martin Langhoff
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=46a038f90509111408f9479e2@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).