From: Tom Tromey <tromey@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: What is keeping GDB in CVS ?
Date: Thu, 25 Jun 2009 21:45:00 -0000 [thread overview]
Message-ID: <m3zlbwdm7e.fsf@fleche.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906201913080.16849@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Sat\, 20 Jun 2009 19\:19\:46 +0000 \(UTC\)")
>>>>> "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
next prev parent reply other threads:[~2009-06-25 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:13 Samuel Bronson
2009-06-19 16:23 ` Daniel Jacobowitz
2009-06-19 16:28 ` Daniel Jacobowitz
2009-06-19 16:38 ` Christopher Faylor
2009-06-19 16:49 ` Daniel Jacobowitz
2009-06-19 16:56 ` Richard Earnshaw
2009-06-19 17:28 ` Daniel Jacobowitz
2009-06-19 17:30 ` Tom Tromey
2009-06-19 19:18 ` Joseph S. Myers
2009-06-19 17:18 ` Joseph S. Myers
2009-06-19 19:22 ` Christopher Faylor
2009-06-19 19:29 ` Joseph S. Myers
2009-06-20 18:48 ` Christopher Faylor
2009-06-20 19:19 ` Joseph S. Myers
2009-06-20 20:36 ` Christopher Faylor
2009-06-20 20:53 ` Jan Kratochvil
2009-06-25 21:45 ` Tom Tromey [this message]
2009-06-26 12:28 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zlbwdm7e.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox