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

2013-02-13 Thread MikeW
MikeW yahoo.co.uk> writes: > > Paul Campbell 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

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

2013-02-13 Thread MikeW
Paul Campbell 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 > Hope that helps. > > -- > Paul > ... Super-Snip ... > >

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

2013-02-12 Thread Paul Campbell
Hi Mike, I think git-cvsimport and git-subtree could help you here. Roughly: # Create a git version of each SDK_subproj git cvsimport -r upstream -d $CVSREPO1 $CVSMODULE1 -C SDK_subproj1 git cvsimport -r upstream -d $CVSREPO2 $CVSMODULE2 -C SDK_subproj2 # Create your Working_SDK git init Workin

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

2013-02-12 Thread MikeW
Matthieu Moy grenoble-inp.fr> writes: > > MikeW 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

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

2013-02-12 Thread Matthieu Moy
MikeW 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

A good Git technique for referring back to original files

2013-02-12 Thread MikeW
Hi, I have a client with an SDK product. Normally the SDK is used in its unpackaged form by the end-user, and that is the directory structure and set of files in which development work on the SDK functionality is performed. However the SDK directory and content is generated from a packager which