From: Christian Couder <chriscool@tuxfamily.org>
To: Sam Hocevar <sam@zoy.org>
Cc: git@vger.kernel.org
Subject: Re: git-p4 workflow suggestions?
Date: Wed, 11 Mar 2009 08:03:12 +0100 [thread overview]
Message-ID: <200903110803.12736.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20090310095729.GA27280@zoy.org>
Le mardi 10 mars 2009, Sam Hocevar a écrit :
> On Tue, Mar 10, 2009, Christian Couder wrote:
> > > I have modified git and git-p4 to a point where they are usable in
> > > my work environment. I am now faced with a new problem: Perforce's
> > > composite workspaces. They allow you to "mount" parts of the repo
> > > onto other directories, even nonempty ones.
> >
> > It looks like SVN externals. So I think you should read about "git
> > submodule".
> >
> > There is this related link on the wiki:
> >
> > http://blog.alieniloquent.com/2008/03/08/git-svn-with-svnexternals/
>
> Unfortunately submodules are considered separate repositories, so if
> I have /include and /src as submodules, I cannot commit atomically to
> both. Or can I? That's probably my strongest requirement.
I thought that you can commit in /include then in /src and then in the
supermodule. This way you should have an atomic commit in the supermodule
with both changes. But I don't know much about submodules.
> > You may also want to search the mailing list as this subject has often
> > been discussed.
>
> I did skim through the archives, but couldn't find much. There was
> this discussion: http://kerneltrap.org/mailarchive/git/2006/11/28/231515
> where the idea of Perforce-like workspaces was apparently dismissed as
> being "a mess".
Perhaps. Anyway I think there are patches about submodules quite often on
the list and it seems a hot topic as there is an entry on the GSoC2009 idea
page:
http://git.or.cz/gitwiki/SoC2009Ideas
On this page you may also be interested by the "Narrow and Sparse clone
support" idea.
Best regards,
Christian.
PS: it would be nice to put me in the CC header of your emails when you
reply to me.
next prev parent reply other threads:[~2009-03-11 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 14:21 git-p4 workflow suggestions? Sam Hocevar
2009-03-10 7:15 ` Christian Couder
2009-03-10 9:57 ` Sam Hocevar
2009-03-11 7:03 ` Christian Couder [this message]
2009-03-11 12:58 ` Pete Wyckoff
2009-03-16 18:01 ` Sam Hocevar
2009-03-17 15:18 ` Pete Wyckoff
2009-03-20 10:31 ` Sam Hocevar
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=200903110803.12736.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=sam@zoy.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 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).