From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Sebastian Staudt <koraktor@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Martin von Zweigbergk <martinvonz@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC] checkout --rebase
Date: Fri, 19 Jul 2013 17:06:59 +0530 [thread overview]
Message-ID: <CALkWK0mp=2xuQwSjMPRBvwRUEnAbM2=r_hZu=ZKc8wxZYxgSVA@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0kVNw3Ko3+_Y-KDF=pdha6wxyMmQmLtOOr5tQYzgUr_Mw@mail.gmail.com>
Ramkumar Ramachandra wrote:
> diff --git a/git-rebase.sh b/git-rebase.sh
> index 0039ecf..7405d9a 100755
> --- a/git-rebase.sh
> +++ b/git-rebase.sh
Er, sorry. I think it suffices to check that $branch_name equals
HEAD, for this optimization.
next prev parent reply other threads:[~2013-07-19 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 10:21 [RFC] checkout --rebase Ramkumar Ramachandra
2013-07-19 10:48 ` Sebastian Staudt
2013-07-19 11:10 ` Ramkumar Ramachandra
2013-07-19 11:33 ` Ramkumar Ramachandra
2013-07-19 11:36 ` Ramkumar Ramachandra [this message]
2013-07-19 12:31 ` Ramkumar Ramachandra
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='CALkWK0mp=2xuQwSjMPRBvwRUEnAbM2=r_hZu=ZKc8wxZYxgSVA@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=koraktor@gmail.com \
--cc=martinvonz@gmail.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).