From: Eugen Konkov <kes-kes@yandex.ru>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: git rebase/git rebase --abort cause inconsistent state
Date: Fri, 6 Nov 2020 20:34:33 +0200 [thread overview]
Message-ID: <992859192.20201106203433@yandex.ru> (raw)
In-Reply-To: <1526558917.20201106203213@yandex.ru>
Hello Eugen,
Friday, November 6, 2020, 8:32:13 PM, you wrote:
> Hi
> I try to rebase, get conflicts. So I decide to --abort
> After --abort I expect state before rebasing, but I get conflicts.
> I supposet this is because `git rebase` switches to not branch and
> --abort can not return to branch I was on before rebasing
> Is this a bug?
> kes@work ~/t/lib/MaitreD $ git rebase dev local/dev
> Created autostash: 566876c8
> warning: Cannot merge binary files: share/ChangeAgreement.docx
> (HEAD vs. f2442d9a... Update Docs.pm)
> Auto-merging share/ChangeAgreement.docx
> CONFLICT (content): Merge conflict in share/ChangeAgreement.docx
> error: could not apply f2442d9a... Update Docs.pm
> Resolve all conflicts manually, mark them as resolved with
> "git add/rm <conflicted_files>", then run "git rebase --continue".
> You can instead skip this commit: run "git rebase --skip".
> To abort and get back to the state before "git rebase", run "git rebase --abort".
> Could not apply f2442d9a... Update Docs.pm
> kes@work ~/t/lib/MaitreD $ git rebase --abort
> Applying autostash resulted in conflicts.
> Your changes are safe in the stash.
> You can run "git stash pop" or "git stash drop" at any time.
> Here is a tree before rebasing:
>> a9597aaa (HEAD -> dev) Use DateTime with correct timezone
>> 822ff801 Add link to Podio into mail
>> 65575afe Update Docs.pm
> | < e0003861 (local/dev) Update podio.t - test person contacts
> | < 28ab8630 Create docdate if agreement is new and update test for that
> | < 208ead68 Specified checking of person
> | < f2442d9a Update Docs.pm
> |/
> o 6d9c2159 (xtucha/test, xtucha/dev) Leave only one example in month
> Here is conflicts:
> HEAD detached from 142c1b15
> Changes to be committed:
> (use "git restore --staged <file>..." to unstage)
> 1 modified: ../../Makefile
> 2 modified: ../../etc/maitre_d.development.conf
> 3 modified: Command/bank_statement.pm
> 4 modified: Command/invoicing.pm
> 5 modified: Command/reminding.pm
> 6 modified: Controller/Cart.pm
> 7 modified: Controller/Saldo.pm
> Unmerged paths:
> (use "git restore --staged <file>..." to unstage)
> (use "git add <file>..." to mark resolution)
> 8 both modified: Controller/Podio.pm
> $ git --version
> git version 2.28.0
history after --abort:
* e0003861 (HEAD, local/dev) Update podio.t - test person contacts
* 28ab8630 Create docdate if agreement is new and update test for that
* 208ead68 Specified checking of person
* f2442d9a Update Docs.pm
* 6d9c2159 (xtucha/test, xtucha/dev) Leave only one example in month
history before rebase:
a9597aaa (HEAD -> dev) Use DateTime with correct timezone
--
Best regards,
Eugen Konkov
next prev parent reply other threads:[~2020-11-06 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 18:32 git rebase/git rebase --abort cause inconsistent state Eugen Konkov
2020-11-06 18:34 ` Eugen Konkov [this message]
2020-11-06 20:27 ` Elijah Newren
2020-11-06 23:13 ` Johannes Sixt
2020-11-09 11:46 ` Eugen Konkov
2020-11-09 18:11 ` Junio C Hamano
2020-11-10 17:59 ` Eugen Konkov
2020-11-10 22:28 ` Johannes Schindelin
2020-11-11 7:10 ` Johannes Sixt
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=992859192.20201106203433@yandex.ru \
--to=kes-kes@yandex.ru \
--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.
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).