From: Alex Riesen <raa.lkml@gmail.com>
To: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>
Cc: Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: Question about handling of heterogeneous repositories
Date: Tue, 29 Nov 2005 21:47:29 +0100 [thread overview]
Message-ID: <20051129204729.GA3033@steel.home> (raw)
In-Reply-To: <20051127131147.GF22159@pasky.or.cz>
Petr Baudis, Sun, Nov 27, 2005 14:11:47 +0100:
> > > >For everyone who have an experience with ClearCase or Perforce (I'm
> > > >sorry for mentioning it) it is what the "mappings" are often used for:
> > > >a project is build together from different parts, which can be worked
> > > >on separately.
> > > >
> > > >I'm trying to introduce git at work, but have to prepare myself for
> > > >possible questions first, and this is one of them :)
>
> This is something e.g. Cogito wants to support, but does not yet.
> Patches welcome.
I wouldn't know what to patch, having no clear picture of the approach
myself, and especially when I don't feel safe using the solution. For
example, how do you go about moving/renaming files between subrepos?
Rename detection will not work, which will be unexpected...
BTW, how does git-mv behave for out-of-tree renaming? How about
inter-repo renaming (remove+add)?
> > > It would certainly be nicer to have git ignore directories that have the
> > > ".git" directory (so long as it's not the top of the repo, that is), but
> > > I haven't had the energy to fix that when there's already a solution
> > > that's simple enough and quite adequate.
> >
> > BTW, will something like "*/.git/*" in info/exclude work? IOW, does *
> > match a "/"?
>
> Nope, but try just '.git' - in case it is not a pathname but just a
> filename (or dirname, for that matter), it will recursively apply to all
> the subtrees.
well, it ignored the ".git"s in the subdirs, not _the_ subdirectories.
I think that can be helped by putting the directories themselves into
.gitignore lists.
next prev parent reply other threads:[~2005-11-29 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 16:50 Question about handling of heterogeneous repositories Alex Riesen
2005-11-22 19:40 ` Andreas Ericsson
2005-11-22 23:22 ` Alex Riesen
2005-11-27 13:11 ` Petr Baudis
2005-11-29 20:47 ` Alex Riesen [this message]
[not found] ` <200511301405.19541.Josef.Weidendorfer@gmx.de>
2005-11-30 13:15 ` Alex Riesen
2005-11-30 13:58 ` Johannes Schindelin
2005-11-30 14:40 ` Josef Weidendorfer
2005-11-30 15:01 ` Alex Riesen
2005-11-30 16:49 ` Josef Weidendorfer
2005-12-01 8:16 ` Alex Riesen
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=20051129204729.GA3033@steel.home \
--to=raa.lkml@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).