From: Jan Hudec <bulb@ucw.cz>
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: Sun, 2 Mar 2008 20:38:16 +0100 [thread overview]
Message-ID: <20080302193816.GA4276@efreet.light.src> (raw)
In-Reply-To: <47C95823.5090006@vilain.net>
On Sun, Mar 02, 2008 at 02:20:35 +1300, Sam Vilain wrote:
> Jakub Narebski 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".
KDE should not be the case. The source for Debian packages is split in
several independent source packages (which are compilable on their own). You
should rarely need more than 1 or 2 (the one you hack + base) checked out.
> 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 :-)
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2008-03-02 19:39 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 [this message]
2008-03-02 21:29 ` Martin Langhoff
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=20080302193816.GA4276@efreet.light.src \
--to=bulb@ucw.cz \
--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).