From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Andrew Wong <andrew.kw.w@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [BUG?] rebase -i: edit versus unmerged changes
Date: Sat, 23 Mar 2013 18:21:22 +0530 [thread overview]
Message-ID: <CALkWK0nspPEaA3BLjgV6Qv2UgXRbDft1d6SmRCiVNJoxpqLFwg@mail.gmail.com> (raw)
In-Reply-To: <7vehf76uai.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> Ramkumar Ramachandra wrote:
>>
>>> I'd really to have that final 'git continue' in Git 2.0. Can someone
>>> attempt to break up the migration path into manageable logical steps
>>> that we can start working on?
>>
>> Is there any deadline or migration path needed? Depending on the
>> design, it might be possible to do without backward-incompatible
>> changes, meaning the migration path is "whatever someone feels like
>> implementing first lands first".
>
> FWIW, I am not convinced yet why we would even want "git continue"
> in the first place, so I won't be the one who would be suggesting a
> migration path.
Okay, I'm confused now. You were the one who suggested a unified "git
continue" in the first place, if my memory serves me right. Why are
you doubting it now?
next prev parent reply other threads:[~2013-03-23 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 9:37 [BUG?] rebase -i: edit versus unmerged changes Ramkumar Ramachandra
2013-03-19 14:21 ` Andrew Wong
2013-03-20 20:25 ` Ramkumar Ramachandra
2013-03-20 20:42 ` Jonathan Nieder
2013-03-20 20:45 ` Junio C Hamano
2013-03-22 8:23 ` Ramkumar Ramachandra
2013-03-22 18:25 ` Jonathan Nieder
2013-03-22 20:42 ` Junio C Hamano
2013-03-23 12:51 ` Ramkumar Ramachandra [this message]
2013-03-24 5:13 ` Junio C Hamano
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=CALkWK0nspPEaA3BLjgV6Qv2UgXRbDft1d6SmRCiVNJoxpqLFwg@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=andrew.kw.w@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).