git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Leam Hall <leamhall@gmail.com>
To: git@vger.kernel.org
Subject: Only track built files for final output?
Date: Tue, 20 Aug 2019 08:21:41 -0400	[thread overview]
Message-ID: <477295c5-f817-e32b-04fd-a41ddfbbac0a@gmail.com> (raw)

Hey all, a newbie could use some help.

We have some code that generates data files, and as a part of our build 
process those files are rebuilt to ensure things work. This causes an 
issue with branches and merging, as the data files change slightly and 
dealing with half a dozen merge conflicts, for files that are in an 
interim state, is frustrating. The catch is that when the code goes to 
the production state, those files must be in place and current.

We use a release branch, and then fork off that for each issue. Testing, 
and file creation, is a part of the pre-merge process. This is what 
causes the merge conflicts.

Right now my thought is to put the "final" versions of the files in some 
other directory, and put the interim file storage directory in 
.gitignore. Is there a better way to do this?

Thanks!

Leam

             reply	other threads:[~2019-08-20 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 12:21 Leam Hall [this message]
2019-08-20 17:46 ` Only track built files for final output? Pratyush Yadav
2019-08-20 18:01   ` Leam Hall
2019-08-20 18:56     ` Pratyush Yadav
2019-08-20 19:42     ` Phil Hord
2019-08-20 18:11   ` Randall S. Becker

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=477295c5-f817-e32b-04fd-a41ddfbbac0a@gmail.com \
    --to=leamhall@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).