Matthieu Moy <Matthieu.Moy <at> grenoble-inp.fr> writes:

> 
> MikeW <mw_phil <at> 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.
> 
Thanks for the reply.

In my work environment both the SDK and the original files are available
(in an enclosing directory).

--SDK_content
  |
  SDK_subproj1-- ...
  |            |
  |            content
  |
  SDK_subproj2- ...
  |            |
  |            content
  |
  SDK_subprojN- ...
  |            |
  |            content
  |
  Working_SDK ... (under git, baseline generated from subproj1..N)
               |
               content derived from subproj1..N


What I had in mind was something I could run over, say, SDK_content
(alternatively, from within Working_SDK, referring back to SDK_content)
which would note the changed files in Working_SDK and locate the
original files in SDK_subproj1..N letting me merge the changes back.


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to