From: Jens Lehmann <Jens.Lehmann@web.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Marc Branchaud" <marcnarc@xiplink.com>,
skillzero@gmail.com, "Jakub Narebski" <jnareb@gmail.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Bryan Larsen" <bryan.larsen@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Avery Pennarun's git-subtree?
Date: Tue, 27 Jul 2010 23:32:58 +0200 [thread overview]
Message-ID: <4C4F508A.8050200@web.de> (raw)
In-Reply-To: <AANLkTim0A0MAmpgAiaYSgYO=YbZ2gc4Upx3MQQopx6DG@mail.gmail.com>
Am 27.07.2010 22:57, schrieb Avery Pennarun:
> One problem with this line of reasoning is that "--recursive" is
> always an option. But if submodules are ever to be easy to use, I
> think it should be the default (or settable as a default using git
> config). This would take us a *long* way towards usability (of
> course, in addition to adding the missing features, as you mention).
And that is exactly what I am currently doing:
- I already teached diff and status to always recurse (and just
sent a patch to add a config option for that behavior, as some
users either can't pay the performance costs or don't want to
see submodules show up as modified just because they contain
untracked files).
- I posted a WIP patch doing recursive checkouts (that is basically
working but I still have to put in the safety checks so that no
modifications to submodules are accidentally discarded unless -f
is used).
- I am working on a recursive fetch too.
And then there is other stuff on my list to be tackled; I try to
fix these issues so that the most annoying problems get solved
first.
Unfortunately that does not proceed as fast as i wished, but
hopefully I can show some progress in the near future. Of course
any help would greatly be appreciated ;-)
next prev parent reply other threads:[~2010-07-27 21:33 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 17:15 Avery Pennarun's git-subtree? Bryan Larsen
2010-07-21 19:43 ` Ævar Arnfjörð Bjarmason
2010-07-21 19:56 ` Avery Pennarun
2010-07-21 20:36 ` Ævar Arnfjörð Bjarmason
2010-07-21 21:09 ` Avery Pennarun
2010-07-21 21:20 ` Avery Pennarun
2010-07-21 22:46 ` Jens Lehmann
2010-07-22 1:09 ` Avery Pennarun
[not found] ` <m31vavn8la.fsf@localhost.localdomain>
2010-07-22 18:23 ` Bryan Larsen
2010-07-24 22:36 ` Jakub Narebski
2010-07-22 19:41 ` Avery Pennarun
2010-07-22 19:56 ` Jonathan Nieder
2010-07-22 20:06 ` Avery Pennarun
2010-07-22 20:17 ` Ævar Arnfjörð Bjarmason
2010-07-22 21:33 ` Avery Pennarun
2010-07-23 15:10 ` Jens Lehmann
2010-07-26 17:34 ` Eugene Sajine
2010-07-22 20:43 ` Elijah Newren
2010-07-22 21:32 ` Avery Pennarun
2010-07-23 8:31 ` Chris Webb
2010-07-23 8:40 ` Avery Pennarun
2010-07-23 15:11 ` Jens Lehmann
2010-07-23 22:33 ` Avery Pennarun
2010-07-23 15:13 ` Jens Lehmann
2010-07-23 15:10 ` Jens Lehmann
2010-07-23 16:05 ` Bryan Larsen
2010-07-23 17:11 ` Jens Lehmann
2010-07-23 19:01 ` Bryan Larsen
2010-07-23 22:32 ` Avery Pennarun
2010-07-25 19:57 ` Jens Lehmann
2010-07-27 18:40 ` Avery Pennarun
2010-07-27 21:14 ` Jens Lehmann
2010-07-23 15:19 ` Marc Branchaud
2010-07-23 22:50 ` Avery Pennarun
2010-07-24 0:58 ` skillzero
2010-07-24 1:20 ` Avery Pennarun
2010-07-24 19:40 ` skillzero
2010-07-25 1:47 ` Nguyen Thai Ngoc Duy
2010-07-28 22:27 ` Jakub Narebski
2010-07-26 13:13 ` Jakub Narebski
2010-07-26 16:37 ` Marc Branchaud
2010-07-26 16:41 ` Linus Torvalds
2010-07-26 17:36 ` Bryan Larsen
2010-07-26 17:48 ` Linus Torvalds
2010-07-27 18:28 ` Avery Pennarun
2010-07-27 20:25 ` Junio C Hamano
2010-07-27 20:57 ` Avery Pennarun
2010-07-27 21:14 ` Junio C Hamano
2010-07-27 21:32 ` Jens Lehmann [this message]
2010-07-26 8:56 ` Jakub Narebski
2010-07-27 18:36 ` Avery Pennarun
2010-07-28 13:36 ` Marc Branchaud
2010-07-28 18:32 ` Jakub Narebski
2010-07-24 20:07 ` Sverre Rabbelier
2010-07-26 8:51 ` Jakub Narebski
2010-07-27 19:15 ` Avery Pennarun
2010-07-26 15:15 ` Marc Branchaud
2010-07-21 23:46 ` Ævar Arnfjörð Bjarmason
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=4C4F508A.8050200@web.de \
--to=jens.lehmann@web.de \
--cc=apenwarr@gmail.com \
--cc=avarab@gmail.com \
--cc=bryan.larsen@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=marcnarc@xiplink.com \
--cc=skillzero@gmail.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.