From: Andreas Ericsson <ae@op5.se>
To: Bill Priest <priestwilliaml@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: git-merge ignore specific files
Date: Tue, 06 Nov 2007 13:53:21 +0100 [thread overview]
Message-ID: <473063C1.7070607@op5.se> (raw)
In-Reply-To: <174134.11501.qm@web55007.mail.re4.yahoo.com>
Bill Priest wrote:
> All,
> I have two branches that are slightly different and
> most changes "belong" in both. There are a handful of
> files/directories that are disparate. Is there any
> way in git to tell it not to merge these files? Kind
> of like .gitignore but for merges.
> In addition I'd like a way to specify to git-merge
> to leave all merged files unrecorded in the index.
> Then as I go through each file making sure that the
> merge "makes sense" (not that git did the right thing;
> but that I want the changes in both branches) that I
> add the change to the index.
> I'm sure that I'm probably using git "incorrectly"
> and I welcome suggestions for modifying my workflow to
> a git style.
>
> Any and all suggestions greatly appreciated,
>
At a cursory glance at the sources, it looks as if you should be able to
get what you want with pretty small modifications to builtin-read-tree.c
and git-merge.sh.
Specifically, 'git read-tree' (which does the heavy lifting during merges)
takes --exclude-per-directory as an argument. You want to teach 'git merge'
to do the same and pass that argument along to 'git read-tree'. Then it's
just a matter of maintaining two sets of .gitignore files, one of which
you'd probably want to call .mergeignore (or something) and make sure you
don't forget to pass that option when you merge (although I assume you'd
notice if you'd forgotten it during conflict resolution).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-06 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 12:38 git-merge ignore specific files Bill Priest
2007-11-06 12:53 ` Andreas Ericsson [this message]
2007-11-06 13:03 ` Jakub Narebski
2007-11-06 13:15 ` Bill Priest
2007-11-06 13:46 ` Jakub Narebski
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=473063C1.7070607@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=priestwilliaml@yahoo.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).