git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brent Goodrick <bgoodr@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Elijah Newren <newren@gmail.com>, git@vger.kernel.org
Subject: Re: How do I force git to forget about merging a binary file that is  to stay deleted on the target branch?
Date: Sat, 28 Mar 2009 08:21:06 -0700	[thread overview]
Message-ID: <e38bce640903280821k79aa241fqded9fc454e266353@mail.gmail.com> (raw)
In-Reply-To: <7viqltvg7n.fsf@gitster.siamese.dyndns.org>

On Sat, Mar 28, 2009 at 8:07 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> You can resolve this merge conflict by running
>> $ git rm TimeSheets/Timesheet\ Exempt.XLS
>>
>> which will make git delete the file from your working copy and the
>> index, at which point you can then make a commit that does not include
>> this file.
>
> But is this what you really want to do?  After doing such a "remove it"
> merge resolution at Home, wouldn't merging it back to Work remove the
> file?

Yes, and I've not told the full story.  Each time I do a merge in
between the two branches, I have a script that resets certain files
that I don't want cross-pollinated between the two branches. Then I do
the commit.  Most of the time (on non-binary files, and/or on files I
only change on the work branch and not on the home branch), this works
just fine.

My desire to avoid doing the above drove my earlier post asking
whether there as a facility to exclude certain files from
participating in merges. But the answer was "no" to that, hence my ad
hoc workaround above.

bg

      reply	other threads:[~2009-03-28 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28  5:26 How do I force git to forget about merging a binary file that is to stay deleted on the target branch? Brent Goodrick
2009-03-28 10:23 ` Nanako Shiraishi
2009-03-28 14:29   ` Brent Goodrick
2009-03-28 12:47 ` Elijah Newren
2009-03-28 14:46   ` Brent Goodrick
2009-03-28 15:07   ` Junio C Hamano
2009-03-28 15:21     ` Brent Goodrick [this message]

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=e38bce640903280821k79aa241fqded9fc454e266353@mail.gmail.com \
    --to=bgoodr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.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.
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).