From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Sam Vilain" <sam@vilain.net>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"eric miao" <eric.y.miao@gmail.com>,
git@vger.kernel.org
Subject: Re: Will git have a baseline feature or something alike?
Date: Mon, 3 Mar 2008 10:29:37 +1300 [thread overview]
Message-ID: <46a038f90803021329g29b19234wab6b626c9d47e7ab@mail.gmail.com> (raw)
In-Reply-To: <47C95823.5090006@vilain.net>
On Sun, Mar 2, 2008 at 2:20 AM, Sam Vilain <sam@vilain.net> wrote:
> > And last, KDE repos should most probably be split into submodules.
>
> Mmm. Everyone always says that; what it really needs I think is someone
> to really take the conversion on board and come up with a workable plan
> on this front. I think the counter-argument to this was "but you always
> want to have 70% of the repository checked out for development".
> Counter-counter argument is "yes but they don't always need to be deep
> clones". Anyway, it's not my baby, just thought I'd let you know about
> it :-)
That sounds a lot like the x.org submodule split. AFAIU, it did
involve some relatively minor changes to configure/build scripts to
handle the submodules being built somewhere other than in a subdir of
the main project. Nothing earth shattering, just small changes to how
the build works, and I think after the initial shakeout everyone's
happy and the development pace is quite a bit faster & more
adventurous.
All of this from bits I read in the x.org dev lists, and some
developer blogs - IANAX.OD
cheers,
m
next prev parent reply other threads:[~2008-03-02 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:23 Will git have a baseline feature or something alike? eric miao
2008-02-29 9:56 ` Sean
2008-02-29 10:38 ` Karl Hasselström
2008-02-29 13:21 ` Jakub Narebski
2008-03-01 7:04 ` Sam Vilain
2008-03-01 12:39 ` Jakub Narebski
2008-03-01 13:20 ` Sam Vilain
2008-03-02 19:38 ` Jan Hudec
2008-03-02 21:29 ` Martin Langhoff [this message]
2008-03-01 14:10 ` eric miao
2008-03-01 14:29 ` Nguyen Thai Ngoc Duy
2008-03-01 15:41 ` Jakub Narebski
2008-03-01 17:30 ` Eyvind Bernhardsen
2008-03-01 18:00 ` Jakub Narebski
2008-03-02 14:04 ` Shawn O. Pearce
2008-03-01 20:43 ` David Brown
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=46a038f90803021329g29b19234wab6b626c9d47e7ab@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=sam@vilain.net \
/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;
as well as URLs for NNTP newsgroup(s).