From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Matt Di Pasquale <liveloveprosper@gmail.com>
Cc: git@vger.kernel.org, Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: git multisite setup
Date: Tue, 17 Nov 2009 01:13:20 +0100 [thread overview]
Message-ID: <20091117001320.GA13074@vidovic> (raw)
In-Reply-To: <13f0168a0911161018r6fc67d29n781cca670a66815b@mail.gmail.com>
The 16/11/09, Matt Di Pasquale wrote:
> In my sites folder i have folders for different sites of mine:
> example.com example2.com, and i also have generic files like an
> includes dir and a .htaccess file that all sites use. what is the best
> way to track the generic files and the different sites?
>
> i was thinking each site has its own .git repo. and then make a .git
> repo for my sites folder but ignore the individual sites dirs.
> actually that's what i'm doing now.
This looks good to me. Why would you like to change?
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-11-17 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 18:18 git multisite setup Matt Di Pasquale
2009-11-17 0:13 ` Nicolas Sebrecht [this message]
2009-11-17 0:17 ` Matt Di Pasquale
2009-11-17 0:50 ` Nicolas Sebrecht
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=20091117001320.GA13074@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=liveloveprosper@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).