All of lore.kernel.org
 help / color / mirror / Atom feed
From: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
To: gbirchmeier@connamara.com
Cc: git@vger.kernel.org
Subject: Re bug report: I was allowed to "git checkout -b" while mid-rebase
Date: Thu, 19 Jun 2025 14:05:56 +0530	[thread overview]
Message-ID: <20250619083556.10619-1-jayatheerthkulkarni2005@gmail.com> (raw)
In-Reply-To: <CAMq4opMBpg4315Q8awm5SQAQa1vms=3KB+SiQkGtCF7thBPjHw@mail.gmail.com>

Oh I had a funny story with rebase too...
Now that I think about it, I think rebase should have some confirmation 
like Y/N type.

I had a similar problem although it was just majorly me being clumsy,
I had rebased and forgot to continue, and formatted patch and then
I didn't see the files it created and sent the email
with *.patch pathspec.

And that made me realise just after hitting enter that I sent a patch 
with a previous commit You can find the thread here.[1]

So I believe there must be a confirmation with a warning something like
Y/N so that people are sure that they are doing stuff like creating a new branch within 
rebase or even sending an email or formatting the patch.

1 - https://lore.kernel.org/git/20250524073055.58092-2-jayatheerthkulkarni2005@gmail.com/

  reply	other threads:[~2025-06-19  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  0:12 bug report: I was allowed to "git checkout -b" while mid-rebase Grant Birchmeier
2025-06-19  0:19 ` Jacob Keller
     [not found] ` <CABURp0orQ-UCzDgJc=STPQZaaEEGwR0GM-GZq_Ty3BXBKYS2iQ@mail.gmail.com>
2025-06-19  2:30   ` Grant Birchmeier
2025-06-19  8:35     ` K Jayatheerth [this message]
2025-06-19 17:31 ` 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=20250619083556.10619-1-jayatheerthkulkarni2005@gmail.com \
    --to=jayatheerthkulkarni2005@gmail.com \
    --cc=gbirchmeier@connamara.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.