From: Nikolay Rykunov <nikolay.rykunov@jetbrains.com>
To: git@vger.kernel.org
Cc: Kirill Likhodedov <kirill.likhodedov@jetbrains.com>
Subject: Rebase merge backend
Date: Fri, 8 May 2020 17:35:00 +0300 [thread overview]
Message-ID: <CAES10x8wG_tBYZLrdyRAo=kU8B+gg65007Afs9jGdUUxL7kUBQ@mail.gmail.com> (raw)
Dear Git community,
Since git rebase was moved to merge backend I can’t find the way how
to get information that branch was fast-forwarded or it was up-to-date
(it was provided by the apply backend). And a similar issue: I can’t
get information about commits skipped during rebase because they
became empty. Using apply backend I could check that because `No
changes — did you forget to use ‘git add’ ` line was printed. Can you
please help with these issues? Are there any ways to get such info?
Thank you!
Nikolay Rykunov
Software Developer in VCS
JetBrains
http://www.jetbrains.com
The Drive to Develop
next reply other threads:[~2020-05-08 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:35 Nikolay Rykunov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 16:31 Rebase merge backend Nikolay Rykunov
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='CAES10x8wG_tBYZLrdyRAo=kU8B+gg65007Afs9jGdUUxL7kUBQ@mail.gmail.com' \
--to=nikolay.rykunov@jetbrains.com \
--cc=git@vger.kernel.org \
--cc=kirill.likhodedov@jetbrains.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).