All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Elijah Newren" <newren@gmail.com>
To: Alan <alan@clueserver.org>
Cc: git@vger.kernel.org
Subject: Re: Can git ignore parts of files
Date: Fri, 14 Nov 2008 13:06:41 -0700	[thread overview]
Message-ID: <51419b2c0811141206s2fcedfa4udc609702299cc366@mail.gmail.com> (raw)
In-Reply-To: <1226690252.6176.9.camel@rotwang.fnordora.org>

On Fri, Nov 14, 2008 at 12:17 PM, Alan <alan@clueserver.org> wrote:
> I have kind of an odd problem that is causing me grief in git.  I figure
> someone has a good solution here.  (Or not, they will soon.)
>
> I have a couple of kernel .config files that are checked into git.  They
> are used to test kernel configurations for the nightly builds where I
> work.
>
> We have a bunch of kernel developers working on drivers.  When they add
> a new driver, they add in the options in the test file to make it
> compile in the test builds.
>
> The problem is that the kernel config file has a timestamp at the top of
> the file that is generated by "make oldconfig" or "make config".  Other
> than removing the timestamp each time manually, is there a way to get
> git to ignore the timestamp on a merge?
>
> What happens is that the authors submit the changes on a branch in most
> cases.  Sometimes they have a version of that file that is quite out of
> date.  When I go to merge, that one file gives me grief 95% of the time.
>
> Is there an easy way around this?  Am I approaching the problem wrong?
> Is there a better way to do this?

Someone wrote a special merge algorithm to handle similar conflicts in
tracked ChangeLog files (see
http://www.mail-archive.com/bug-gnulib@gnu.org/msg09183.html).
Perhaps you could write a similar merge algorithm and use it?

Hope that helps,
Elijah

  parent reply	other threads:[~2008-11-14 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 19:17 Can git ignore parts of files Alan
2008-11-14 19:33 ` Francis Galiegue
2008-11-14 19:58   ` Alan
2008-11-14 20:06 ` Elijah Newren [this message]
2008-11-16  8:37 ` 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=51419b2c0811141206s2fcedfa4udc609702299cc366@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=alan@clueserver.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.