From: Deon George <deon.george@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Feature Enhancement Idea.
Date: Thu, 24 Sep 2009 19:25:34 +1000 [thread overview]
Message-ID: <5b5e291e0909240225q49a202abk7cf1a0c8f715ad5f@mail.gmail.com> (raw)
In-Reply-To: <m3bpl0c2cf.fsf@localhost.localdomain>
Jakub Narebski wrote:
> First, I assume there that you do not allow for the same file to
> belong to different repositories.
Well, no, I cant see why a file cannot belong to both repositories.
I'm sure it would be easier if a file did belong to a unique
repository, but given that GIT operates at a content layer (from what
I've read anyway), I cant see why it couldnt belong to more than one.
> you can try either submodules
> (git-submodule), or subtree (subtree merge, or third-party git-subtree
> helper).
I had a quick look at submodule - I dont think it helps me anyway,
since I want the flexibility for files to belong to many
sub-directories - not all under 1 sub directory hierarchy.
> Third, if the above isn't what you want, then you can manually
> intermingle working directories of different git repositories
> (probably requiring decouplig of bare git repository (git-dir)
> from working area (work-tree)).
Ahh, now this sounds like it might be what I want to do - I think I'll
explore this. I can see that it would provide file level autonomy
only, but as a starting point I think it will help heaps...
I'll work on it as time permits and come up with some scripts to
provide what I am after (need to learn more on the workings of GIT
first - everyday I learn a new feature :)
Thanks for your idea...
...deon
next prev parent reply other threads:[~2009-09-24 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 6:17 Feature Enhancement Idea Deon George
2009-09-23 8:26 ` Christian Couder
2009-09-23 9:06 ` Johan Herland
2009-09-23 11:12 ` Deon George
2009-09-23 18:17 ` Ciprian Dorin, Craciun
2009-09-23 23:19 ` Johan Herland
2009-09-23 20:08 ` Junio C Hamano
2009-09-24 5:52 ` Deon George
2009-09-24 5:56 ` Jakub Narebski
2009-09-24 9:25 ` Deon George [this message]
2009-09-24 16:45 ` Eric Raible
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=5b5e291e0909240225q49a202abk7cf1a0c8f715ad5f@mail.gmail.com \
--to=deon.george@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).