From: Andreas Ericsson <ae@op5.se>
To: Mike Sharov <msharov@users.sourceforge.net>
Cc: git@vger.kernel.org
Subject: Re: How can I track a template?
Date: Sun, 07 Sep 2008 21:35:58 +0200 [thread overview]
Message-ID: <48C42D1E.8000805@op5.se> (raw)
In-Reply-To: <48C3FB9E.8090404@users.sourceforge.net>
Mike Sharov wrote:
> I am trying to create a standard module to be included into many
> projects. Specifically, the build system skeleton, but I have other uses
> for the same mechanism. The idea is to have a repository with the
> skeleton itself, and have other projects include it somehow and keep
> up-to-date by pulling from the template repository.
>
> The straightforward approach of using 'git pull' does not work very
> well. At each merge, all the things changed show up. For example, I
> would change the project name in the configure template. This change
> creates a merge conflict on every pull even if that particular line did
> not change in the template. Somehow it just doesn't seem to establish a
> base for the merges. Another problem is that the tags get pulled and
> become tags on the project, which is undesirable.
>
> What sort of a solution would you recommend for this, if any?
Enable rerere, the merge resolution recorder/replayer.
Pull from skeleton repo with --no-tags, and remove the tag-fetching
refspec from your .git/config (note that everyone has to do it, but
if only you integrate the updated skeleton that won't be a problem).
Or unconditionally include a project.mak (or some such) from the build
skeleton which sets all the project-specific details.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2008-09-07 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 16:04 How can I track a template? Mike Sharov
2008-09-07 19:35 ` Andreas Ericsson [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=48C42D1E.8000805@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=msharov@users.sourceforge.net \
/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.