From: Max Kirillov <max@max630.net>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Duy Nguyen <pclouds@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH/RFC v2] Squashed changes for multiple worktrees vs. submodules
Date: Sun, 7 Dec 2014 11:15:03 +0200 [thread overview]
Message-ID: <20141207091503.GC9128@wheezy.local> (raw)
In-Reply-To: <20141207064230.GA9782@wheezy.local>
On Sun, Dec 07, 2014 at 08:42:30AM +0200, Max Kirillov wrote:
>> *) I'd love to see a solution for sharing the object database
>> between otherwise unrelated clones of the same project (so
>> that fetching in one clone updates the objects in the common
>> dir and gc cannot throw anything away used by one of the
>> clones). But I'd expect a bare repository as the common one
>> where we put the worktrees refs into their own namespaces.
> There is a GIT_NAMESPACE already, maybe it should be just
> extended to work with all commands?
No, this will not work for submodules, has same issues with
the same config.
next prev parent reply other threads:[~2014-12-07 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 23:27 [PATCH/RFC v2] Squashed changes for multiple worktrees vs. submodules Max Kirillov
2014-12-01 10:43 ` Duy Nguyen
2014-12-01 14:47 ` Max Kirillov
2014-12-02 20:45 ` Jens Lehmann
2014-12-02 22:16 ` Max Kirillov
2014-12-04 20:06 ` Jens Lehmann
2014-12-05 1:33 ` Duy Nguyen
2014-12-06 12:44 ` Jens Lehmann
2014-12-05 6:32 ` Max Kirillov
2014-12-06 13:06 ` Jens Lehmann
2014-12-07 6:42 ` Max Kirillov
2014-12-07 9:15 ` Max Kirillov [this message]
2014-12-08 20:40 ` Jens Lehmann
2014-12-08 21:49 ` Max Kirillov
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=20141207091503.GC9128@wheezy.local \
--to=max@max630.net \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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;
as well as URLs for NNTP newsgroup(s).