From: Sergey Organov <sorganov@gmail.com>
To: Chris Torek <chris.torek@gmail.com>
Cc: Hongyi Zhao <hongyi.zhao@gmail.com>,
Phillip Susi <phill@thesusis.net>, Git List <git@vger.kernel.org>
Subject: Re: git revert with partial commit.
Date: Tue, 04 Apr 2023 20:21:18 +0300 [thread overview]
Message-ID: <87lej7zhpt.fsf@osv.gnss.ru> (raw)
In-Reply-To: <CAPx1Gvcz6f3AQJYfq7Sih0bL6pAi5mHZj8rj=kd7kRDWKLZEzw@mail.gmail.com> (Chris Torek's message of "Tue, 4 Apr 2023 09:19:35 -0700")
Chris Torek <chris.torek@gmail.com> writes:
> On Tue, Apr 4, 2023 at 9:00 AM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
> [various previous conversations and methods-that-work snipped]
>> But I still wonder why the following method doesn't work:
>>
>> werner@X10DAi:~$ git revert f18fbd1e16a1ca4215621768d17858c036086608
>> --no-commit -- Public/CTAN/IDE/phonon/compile-install-phonon
>> Public/CTAN/IDE/texstudio-org/texstudio.git.sh
>> fatal: bad revision 'Public/CTAN/IDE/phonon/compile-install-phonon'
[...]
> Similarly, `git revert` means: given some commit, find its parent
> (again, singular), and use that parent/child pair to compute a
> delta. Attempt to reverse-apply that delta to the current commit
> and working tree snapshot.
>
> This kind of operation produces a new commit, so there's no such
> thing as a partial revert or partial cherry-pick, at least in
> terms of "things Git can do by itself". But we, as humans writing
> programs, wish to *achieve* such things.
So, why Git can't help us achieving it by supporting paths limiting in
(all) merge operations? There seems to be no absolute obstacles, just a
luck of support.
Thanks,
-- Sergey
next prev parent reply other threads:[~2023-04-04 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 9:17 git revert with partial commit Hongyi Zhao
2023-04-02 14:16 ` Torsten Bögershausen
2023-04-03 17:07 ` Junio C Hamano
2023-04-04 0:28 ` Hongyi Zhao
2023-04-03 18:29 ` Phillip Susi
2023-04-04 0:20 ` Hongyi Zhao
2023-04-04 0:37 ` Hongyi Zhao
2023-04-04 15:50 ` Hongyi Zhao
2023-04-04 16:19 ` Chris Torek
2023-04-04 17:21 ` Sergey Organov [this message]
2023-04-04 18:20 ` Junio C Hamano
2023-04-04 19:40 ` Sergey Organov
2023-04-04 19:48 ` Junio C Hamano
2023-04-04 21:14 ` Felipe Contreras
2023-04-05 6:39 ` Sergey Organov
2023-04-07 0:24 ` Felipe Contreras
2023-04-07 17:20 ` Sergey Organov
2023-04-06 15:48 ` Phillip Susi
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=87lej7zhpt.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=hongyi.zhao@gmail.com \
--cc=phill@thesusis.net \
/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).