From: Len Brown <len.brown@intel.com>
To: git@vger.kernel.org
Subject: needs merge
Date: Sat, 7 Jan 2006 03:32:36 -0500 [thread overview]
Message-ID: <200601070332.36654.len.brown@intel.com> (raw)
a merge results in multiple conflict files.
some of the files are resolved by editing and picking changes from both branches.
but some files I want to ignore the new changes and keep what was originally there.
However, if I restore what was originally in the destination
either by editing the destination and ending up with what i started with,
or via git checkout on the file, i get
$ git commit
my-file needs merge
how do i tell git that there is no merge to do and the (unchanged) working file is what
i want to keep as the result of the merge?
i recall running into this a long time ago and i added blank line to the destination file
and that made git happy, but maybe i shouldn't have to resort to that, yes?
thanks,
-Len
next reply other threads:[~2006-01-07 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 8:32 Len Brown [this message]
2006-01-07 8:41 ` needs merge Junio C Hamano
2006-01-07 8:57 ` Len Brown
2006-01-07 10:28 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 10:33 Brown, Len
2006-01-07 21:06 ` Junio C Hamano
2006-01-10 5:21 ` Daniel Barkalow
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=200601070332.36654.len.brown@intel.com \
--to=len.brown@intel.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).