From: Eugene Sajine <euguess@gmail.com>
To: git@vger.kernel.org
Cc: Eugene Sajine <euguess@gmail.com>
Subject: how to fix the problem correctly?
Date: Wed, 28 Apr 2010 12:54:33 -0400 [thread overview]
Message-ID: <w2t76c5b8581004280954r436c1be1g8d6e415bf3596f4d@mail.gmail.com> (raw)
I have a following situation (in dev branch):
3 files:
1.txt, 2.txt, 3.txt
A -> B -> C -> D -> E
| |
Master dev
Between B and C the version of file 1.txt was screwed up (let’s say it
was copied into git repo from other location where it was in state A
(CVS) and then committed by mistake in C, effectively reverting the
change of this file in commit B)
Commit C also had changes to files 2 and 3.
After this commits D and E did not have changes for file 1.txt, only 2
and 3 were touched.
When we tried to revert commit C – this lead to the code completely
messed up, with conflicts – so this seems to be not an option.
Rebase also doesn’t seem to help here
Only two variants I saw:
1. Do “git co A 1.txt” and commit the change as F
2. Do “git reset –soft master” and recommit all changes once again
Is there a better way?
PS interesting enough – CVS keywords helped us to notice the problem
as master state was imported from CVS.
In commit A file 1.txt had version ID 1.5 in commit B it was 1.6 ,
commit C was changing the line back to 1.5
Is there a way for git to help me to recognize this kind of issue if
there are no keywords?
DISCLAIMER: I don’t like keywords, and I don’t want them to be
implemented in git.
Thanks,
Eugene
next reply other threads:[~2010-04-28 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 16:54 Eugene Sajine [this message]
2010-04-28 18:30 ` how to fix the problem correctly? Avery Pennarun
2010-04-28 18:55 ` Eugene Sajine
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=w2t76c5b8581004280954r436c1be1g8d6e415bf3596f4d@mail.gmail.com \
--to=euguess@gmail.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 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).