From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Gareth Collins <gareth.o.collins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git subtree push-all and pull-all
Date: Sun, 7 Jul 2013 14:54:30 +0200 [thread overview]
Message-ID: <20130707125430.GA23197@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CALemSr4Z+p7v_wQn7EOFTVHjtMYgxqGSBZf3zU5pn-eW_SEG5A@mail.gmail.com>
On Wed, Jul 03, 2013 at 03:56:36PM -0400, Gareth Collins wrote:
> Hello,
>
> I see over the last year (on the web and in this mailing list) there
> was some activity to extend subtree with a .gittrees file and
> push-all/pull-all commands.
>
> Perhaps I missed it, but looking through the latest git code on the
> github mirror I can't find any reference to the .gittrees file or
> these commands.
>
> Does anyone know the status of this feature? Was it decided that this
> was a bad idea and the feature has been rejected? Or is this a feature
> still "cooking"...which will likely make it into git mainline at some
> point?
>
> I ask because I would like to use something like this to be able to
> keep a combined repository and separate project repositories in sync.
> Of course, if it was decided that this feature is fundamentally a bad
> idea then I will do something different.
>
> Any pointers would be a big help.
>
> thanks in advance,
> Gareth Collins
Still no answer to this? I suggest that you CC the persons discussing
this the last time.
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2013-07-07 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:56 git subtree push-all and pull-all Gareth Collins
2013-07-07 12:54 ` Fredrik Gustafsson [this message]
2013-07-08 15:20 ` Gareth Collins
2013-07-09 9:21 ` Herman van Rink
2013-07-22 19:35 ` Paul Campbell
2013-07-25 10:00 ` Herman van Rink
2013-07-25 11:19 ` Paul Campbell
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130707125430.GA23197@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=gareth.o.collins@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).