From: Gioele Barabucci <gioele@svario.it>
To: git@vger.kernel.org
Cc: Heiko Voigt <hvoigt@hvoigt.net>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] add update to branch support for "floating submodules"
Date: Sat, 10 Dec 2011 14:16:22 +0000 [thread overview]
Message-ID: <4EE369B6.7060602@svario.it> (raw)
In-Reply-To: <7vr51htbsy.fsf@alter.siamese.dyndns.org>
On 09/11/2011 18:01, Junio C Hamano wrote:
>> This is almost ready but I would like to know what users of the
>> "floating submodule" think about this.
>
> I do like to hear from potential users as well, because the general
> impression we got was that floating submodules is not a real need of
> anybody,
Floating modules are something much sought after by those who use Git
for non-development purposes, like those who have most of their $HOME
versioned with Git [1]. For example, part of what Joey Hess's `mr` tool
[2] does is to simulate floating submodules for Git-versioned $HOMEs.
In the context of versioned $HOMEs, or with backups in general, precise
tracking of submodules updates is not that important. To quote [3]:
«Last, change tracking is a bit more lenient with home directories. I
may shuffle some stuff around, and I don't need to explain the changes
to anyone else.». In my case, I want my ~/Documents dir (that is in a
different repo from $HOME) to be always updated; I would prefer not to
deal with submodule updates, merges and detached HEADs.
Bye,
[1] http://vcs-home.branchable.com/
[2] http://kitenet.net/~joey/code/mr/
[3] http://joshcarter.com/productivity/svn_hg_git_for_home_directory
--
Gioele Barabucci <gioele@svario.it>
prev parent reply other threads:[~2011-12-10 14:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:40 [RFC/PATCH] add update to branch support for "floating submodules" Heiko Voigt
2011-11-09 18:01 ` Junio C Hamano
2011-11-29 22:08 ` Heiko Voigt
2011-12-10 5:50 ` Leif Gruenwoldt
2011-12-10 6:19 ` Jonathan Nieder
2011-12-10 6:30 ` Junio C Hamano
2011-12-10 15:27 ` Leif Gruenwoldt
2011-12-12 15:34 ` Andreas T.Auer
2011-12-12 18:04 ` Leif Gruenwoldt
2011-12-12 18:42 ` Andreas T.Auer
2011-12-12 19:13 ` Leif Gruenwoldt
2011-12-12 22:31 ` Jens Lehmann
2011-12-12 22:56 ` Phil Hord
2011-12-13 15:35 ` Marc Branchaud
2011-12-13 21:19 ` Jens Lehmann
2011-12-13 22:42 ` Marc Branchaud
2011-12-12 19:36 ` Junio C Hamano
2011-12-13 14:17 ` Phil Hord
2011-12-13 21:09 ` Jens Lehmann
2012-01-30 21:15 ` Phil Hord
2012-01-31 20:55 ` Jens Lehmann
2012-01-31 22:50 ` Phil Hord
2012-02-01 22:37 ` Jens Lehmann
2012-02-06 17:31 ` Phil Hord
2012-02-06 21:32 ` Jens Lehmann
2011-12-13 0:12 ` Brandon Casey
2011-12-10 14:16 ` Gioele Barabucci [this message]
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=4EE369B6.7060602@svario.it \
--to=gioele@svario.it \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.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 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.