From: Alex Riesen <raa.lkml@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Use diff* with --exit-code in git-am, git-rebase and git-merge-ours
Date: Sun, 25 Mar 2007 01:49:53 +0100 [thread overview]
Message-ID: <20070325004953.GC11507@steel.home> (raw)
In-Reply-To: <20070325004256.GB11507@steel.home>
Alex Riesen, Sun, Mar 25, 2007 01:42:56 +0100:
> This simplifies the shell code and reduces memory footprint, speeds
> things up. The performance improvements should be noticable by
> git-rebase, when it is used to rebase big commits.
Please ignore, I forgot about "--quiet implies --exit-code" again.
Just documented the option. Will resend.
next prev parent reply other threads:[~2007-03-25 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 0:42 [PATCH] Use diff* with --exit-code in git-am, git-rebase and git-merge-ours Alex Riesen
2007-03-25 0:49 ` Alex Riesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-25 0:56 Alex Riesen
2007-03-25 6:01 ` Junio C Hamano
2007-03-25 9:33 ` Alex Riesen
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=20070325004953.GC11507@steel.home \
--to=raa.lkml@gmail.com \
--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).