From: Chaitanya Tata <chaitanya.tk17@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Add support for `git rebase -no-edit`
Date: Fri, 12 Jan 2024 03:16:29 +0530 [thread overview]
Message-ID: <CADA7-FPFb5vmcT+9drdo=bYnixisvMiBqC5x8dPvFt61+FjsVw@mail.gmail.com> (raw)
In-Reply-To: <ZaBgqlR5F1dv9ttg@nand.local>
On Fri, Jan 12, 2024 at 3:12 AM Taylor Blau <me@ttaylorr.com> wrote:
>
> On Thu, Jan 11, 2024 at 01:30:55PM -0800, Junio C Hamano wrote:
> > Chaitanya Tata <chaitanya.tk17@gmail.com> writes:
> >
> > > Hi,
> > >
> > > I have a feature request to add `--no-edit` option to `git rebase`
> > > like we do for `git commit`.
> > > The workflow I typically follow is:
> > >
> > > * `git commit -a --fixup=XXX`
> > > * `git rebase -i HEAD~15 --autosquash`
> > >
> > > But it requires closing the editor without any changes. I can
> > > workaround this using the `GIT_EDITOR` option, see [1]. But it would
> > > be good to have this built-in.
> > >
> > > Thoughts?
> >
> > With what is in the 'master' branch, you do not have to say
> > interactive when you do not want to go interactive. I.e.
> >
> > $ git rebase --autosquash HEAD~15
> >
> > should work fine. Building Git from the source should not be too
> > hard.
Amazing, exactly what I need. And or arg order, I just typed in the command,
I typically use aliases that are in the proper order, but thanks.
>
> Oh, duh. Indeed, 297be59456 (rebase: support --autosquash without -i,
> 2023-11-14) will do what Chaitanya is looking for. I'll give myself pass
> on remembering that patch since it is from last year ;-).
:).
Thanks both for prompt support, I will compile and test this.
prev parent reply other threads:[~2024-01-11 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 17:25 Add support for `git rebase -no-edit` Chaitanya Tata
2024-01-11 19:55 ` Taylor Blau
2024-01-11 20:07 ` Chaitanya Tata
2024-01-11 21:30 ` Junio C Hamano
2024-01-11 21:42 ` Taylor Blau
2024-01-11 21:46 ` Chaitanya Tata [this message]
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='CADA7-FPFb5vmcT+9drdo=bYnixisvMiBqC5x8dPvFt61+FjsVw@mail.gmail.com' \
--to=chaitanya.tk17@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).