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

Re: A good Git technique for referring back to original files

From
MMikeW <mw_phil@yahoo.co.uk>
Date
Feb 13, 2013, 12:50 UTC
Message-ID
<loom.20130213T134501-179@post.gmane.org>
In-Reply-To
<loom.20130213T123734-484@post.gmane.org>
MikeW <mw_phil <at> yahoo.co.uk> writes:
Show 14 quoted lines
> 
> Paul Campbell <pcampbell <at> kemitix.net> writes:
> 
> > 
> > Hi Mike,
> > 
> > I think git-cvsimport and git-subtree could help you here.
> > 
> 
> That looks very interesting, had not considered git subtree and it looks like
> the right kind of method.
> 
> Thanks.
> Mike

The only alternative I can think of is to scan through Working_SDK and replace the files there with symlinks back to the matching files within the original subprojects - such scripts exist !

Then any changes in Working_SDK will update the (baselined) originals in-place.

But then no explicit use of git except for tracking work prior to pushing back to CVS.

Oh well, thanks for ideas, will see which work best.
Mike
Previous: MikeW
Message 6 of 6 in “A good Git technique for referring back to original files”
  1. MikeWFeb 12, 2013
  2. Matthieu MoyFeb 12, 2013
  3. MikeWFeb 12, 2013
  4. Paul CampbellFeb 12, 2013
  5. MikeWFeb 13, 2013
  6. MikeWFeb 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.