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
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Feb 12, 2013, 08:56 UTC
Message-ID
<vpq1ucl9agt.fsf@grenoble-inp.fr>
In-Reply-To
<loom.20130212T085620-989@post.gmane.org>
MikeW <mw_phil@yahoo.co.uk> writes:
> Since git is so good at tracking file content, I wondered whether there was any
> technique using git that would simplify the back-referencing task.

I'm not sure I understand the question, but if you want to add meta-data to Git commits (e.g. "this Git commit is revision 42 in CVS repository foo"), then have a look at git-notes. It won't give you directly "reference to other VCS", but at least can be used as a storage mechanism to store these references.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: MikeWNext: MikeW
Message 2 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.