This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: What is keeping GDB in CVS ?


>>>>> "Joseph" == Joseph S Myers <joseph@codesourcery.com> writes:

Joseph> It seems quite clear to me that all these files should be automatically 
Joseph> tagged when the projects using them are tagged and branched when those 
Joseph> projects are branched and the tagged or branched versions should be 
Joseph> checked out automatically when the tag or branch is checked out.

I looked into the situation a bit more.

My understanding is that the git "submodules" feature only works for
subdirectories of the tree.  It would not therefore work directly for
'src', due to the top-level configury.  It could be made to work, by
requiring some pre-configure command to make symlinks or shuffle files
around.

I still think the best approach is to have a single "infra" repository
holding the shared bits, which is then merged as-needed into other
repositories.  But, there are even issues with this.  One is, what
history do we use to initially populate this repository?  (Maybe it
doesn't matter due to all the double commits.)  The other is, this
would require changes to how gcc handles this code; and since gcc uses
svn I suppose (but don't know for sure) that it would be a pain.

I haven't looked into the "repo" tool that Jan mentioned, yet.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]