From: Junio C Hamano <gitster@pobox.com>
To: Victor Toni <victor.toni@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: Aborting git rebase --edit-todo
Date: Sun, 06 Sep 2020 14:52:28 -0700 [thread overview]
Message-ID: <xmqqft7u4lpf.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: CAG0OSgdT+ZCT0dN29A89XhWi65SFepwyGA0SoS22TYGrvNnWqw@mail.gmail.com
Victor Toni <victor.toni@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>>
>> Victor Toni <victor.toni@gmail.com> writes:
>>
>> > Personally I would like to see your approach (1,2,3) implemented
>> > because it is not destructive. If the user wants to achieve something
>> > different he can retry.
>>
>> Obviously I agree that the approach would be nicer than the status
>> quo. It would not be as trivial as a microproject, but would be a
>> good bite-sized starter-task for those aspiring developers who want
>> to dip their toes in the water to start hacking on the codebase ;-)
>>
> Nice try ;)
For the record I didn't try _you_.
I was writing for general audience, among which there are aspiring
developers seeking a starter-task. Whether you are part of that
audience was immaterial (even though it would have been nice if you
were) ;-).
Thanks.
next prev parent reply other threads:[~2020-09-06 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:39 Aborting git rebase --edit-todo Victor Toni
2020-09-03 17:43 ` Junio C Hamano
2020-09-03 18:55 ` Carlo Arenas
2020-09-03 19:22 ` Victor Toni
2020-09-03 20:02 ` Junio C Hamano
2020-09-03 19:32 ` Victor Toni
2020-09-03 19:59 ` Carlo Arenas
2020-09-03 21:07 ` Victor Toni
2020-09-03 21:08 ` Junio C Hamano
2020-09-03 21:21 ` Victor Toni
2020-09-04 5:43 ` Johannes Schindelin
2020-09-06 21:52 ` Junio C Hamano [this message]
2020-09-04 5:42 ` Johannes Schindelin
2020-09-04 5:32 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqft7u4lpf.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=victor.toni@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).