From: Jens Lehmann <Jens.Lehmann@web.de>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Publishing "filtered branch repositories" - workflow / recommendations?
Date: Thu, 05 Dec 2013 20:54:29 +0100 [thread overview]
Message-ID: <52A0D9F5.3030101@web.de> (raw)
In-Reply-To: <CACPiFCKHprB_oO_eXMYkey_CGbT7WOn5VDDjBdHbLRzcDpHnZw@mail.gmail.com>
Am 05.12.2013 20:27, schrieb Martin Langhoff:
> On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>> Without knowing more I can't think of a reason why submodules should
>> not suit your use case (but you'd have to script branching and tagging
>> yourself until these commands learn to recurse into submodules too).
>
> The submodules feature is way too fiddly and has abundant gotchas.
Care to explain what bothers you the most? Being one of the people
improving submodules I'm really interested in hearing more about that.
> I am diving into subtrees, and finding it a lot more workable.
Yep, for exporting parts of your repo as separate repos one way
subtree might be just what you want.
next prev parent reply other threads:[~2013-12-05 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:01 Publishing "filtered branch repositories" - workflow / recommendations? Martin Langhoff
2013-12-05 18:43 ` Martin Langhoff
2013-12-05 19:18 ` Jens Lehmann
2013-12-05 19:27 ` Martin Langhoff
2013-12-05 19:54 ` Jens Lehmann [this message]
2013-12-05 22:06 ` Martin Langhoff
2013-12-06 8:48 ` Jens Lehmann
2013-12-06 19:40 ` Martin Langhoff
2013-12-09 22:59 ` Heiko Voigt
2013-12-09 23:56 ` Junio C Hamano
2013-12-11 22:03 ` Jens Lehmann
2013-12-11 23:16 ` Junio C Hamano
2013-12-12 13:39 ` Heiko Voigt
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=52A0D9F5.3030101@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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).