git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Mapping file contents from one repository to another

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
May 13, 2013, 08:46 UTC
Message-ID
<5190A873.2040101@alum.mit.edu>
In-Reply-To
<1368372120.73994.YahooMailNeo@web160305.mail.bf1.yahoo.com>
On 05/12/2013 05:22 PM, Jason Timrod wrote:
Show 11 quoted lines
> Hi all,
> 
> This is a complicated question to try and ask, let alone answer, so I had best give some background.
> 
> I have two repositories --- one of them, which I'll call "repoA", is the main repository, it's the one which most of the code we develop ends up.  The other repository, "repoB" is our portable version of the code---the one which is used to deploy on systems other than the one which repoA is deployed on.  As such, "repoB" often (and does) contain commits specific to repoB which will never appear in repoA, such as OS-specific things.
> 
> In this case, in repoA we have a man page.  Up until recently, this used to be the same file in both repositories.  But because of the way the files in repoB are deployed, unlike in repoA this file has had its name changed from:
> 
> foo.1 -> foo.1.in
> 
> Because the man page is run through some sed script to replace various things which never need to happen in repoA

Why don't you name it foo.1.in in both repos and pipe it through "cat" on repoA (i.e., just copy it to foo.1)? Then you would only have to maintain a small difference in your build system between repoA/repoB rather than having to coordinate two versions of the bigger source document.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Jason Timrod
Message 2 of 2 in “Mapping file contents from one repository to another”
  1. Jason TimrodMay 12, 2013
  2. Michael HaggertyMay 13, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.