From: Jim Meyering <jim@meyering.net>
To: tromey@redhat.com
Cc: "H.J. Lu" <hjl.tools@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 16:21:00 -0000 [thread overview]
Message-ID: <87pr90334a.fsf@meyering.net> (raw)
In-Reply-To: <m3skdw5wxa.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 06 Oct 2009 10:06:41 -0600")
Tom Tromey wrote:
>>>>>> "Jim" == Jim Meyering <jim@meyering.net> writes:
> Jim> Since some directories are shared between projects, one way would
> Jim> be to make each directory into its own git repository.
> Jim> Then, a separate gdb.git repository would include them
> Jim> via a git submodule.
>
> I thought that submodules could not be used to share files in the
> top-level directory. This is why I think submodules are not a viable
> solution for src -- anything in that directory is shared, not only by
> all the src projects, but also by gcc.
You can put the top-level files in their own repository and make that
a submodule, then have either a VC'd symlink for each file (ugly, and
not as maintainable, IMHO) or a bootstrap/autogen.sh-style script that
creates the links.
next prev parent reply other threads:[~2009-10-06 16:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 0:31 H.J. Lu
2009-10-06 6:23 ` Pierre Muller
2009-10-06 6:45 ` Jim Meyering
2009-10-06 6:51 ` Jim Meyering
2009-10-06 7:38 ` Jim Meyering
2009-10-06 13:08 ` H.J. Lu
2009-10-06 14:07 ` Jim Meyering
2009-10-06 14:26 ` Joseph S. Myers
2009-10-06 14:33 ` Jim Meyering
2009-10-06 16:11 ` Joseph S. Myers
2009-10-07 4:29 ` Matt Rice
2009-10-10 5:35 ` Matt Rice
2009-10-06 16:06 ` Tom Tromey
2009-10-06 16:21 ` Jim Meyering [this message]
2009-10-06 15:45 ` Joel Brobecker
2009-10-06 18:38 ` Eli Zaretskii
2009-10-06 19:01 ` Joel Brobecker
2009-10-06 20:36 ` Eli Zaretskii
2009-10-06 21:10 ` Joel Brobecker
2009-10-06 22:04 ` Tom Tromey
2009-10-07 7:29 ` Eli Zaretskii
2009-10-07 7:27 ` Eli Zaretskii
2009-10-06 16:08 ` Tom Tromey
2009-10-06 16:09 ` Jim Meyering
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=87pr90334a.fsf@meyering.net \
--to=jim@meyering.net \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=tromey@redhat.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