git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Renato Botelho <rbgarga@gmail.com>
To: git@vger.kernel.org
Subject: Ignoring svn custom id lines on merge
Date: Fri, 22 May 2009 17:30:27 -0300	[thread overview]
Message-ID: <747dc8f30905221330r691dc58cwf21a0070e9652aaf@mail.gmail.com> (raw)

Hello,

I'm starting tests to move from cvs to git, and i got just one
problem on all my tests.

We maintain a custom copy of FreeBSD sources, so, on
cvs we did follow when new FreeBSD version is released:

1. Import new freebsd src as a vendor branch
2. Merge changes on HEAD

I tried to do the same with git, and it worked, but since
almost all FreeBSD files has a custom Id like this:

$FreeBSD: release/7.0.0/COPYRIGHT 175036 2008-01-01 09:36:30Z imp $

These lines always change, because the place they stay
on svn repository (release/7.0.0, 7.1.0, 7.2.0) and git
generated a lot of conflicts to fix manually.

I would like to know if there is a way to configure git to
just ignore diffs on these lines and use the new one without
ask.

I can do it with diff command ignoring those lines, like this:

diff -q -I'[$]FreeBSD:.*$'

Thank you in advance
-- 
Renato Botelho

                 reply	other threads:[~2009-05-22 20:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=747dc8f30905221330r691dc58cwf21a0070e9652aaf@mail.gmail.com \
    --to=rbgarga@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).