From: Matt Di Pasquale <liveloveprosper@gmail.com>
To: git@vger.kernel.org
Subject: Fwd: how to apply patch?
Date: Sat, 6 Feb 2010 21:05:39 -0500 [thread overview]
Message-ID: <13f0168a1002061805o5d64c05cy9d8f0190a8f37feb@mail.gmail.com> (raw)
In-Reply-To: <13f0168a1002061720t93ff6aew3420a41a547549d8@mail.gmail.com>
I have a development version & a production version of my website.
There are a few essential differences between them that I want to
always stay different (like path constants, etc). When I make changes
on the dev version and test it out and they work and am ready to copy
them to the production (www) version, how do i do that without
annihilating the essential differences that i want to keep? I was
thinking of creating a patch or branch or something with the
differences. Then, copy dev to pro, then reapply/rebase the essential
differences to pro that got wiped out. if i rebase though, i want to
be able to rebase again on the next edit.
what's a good way to do this?
My dir structure:
example.com
www # production site
dev # development site
Via DreamHost control panel:
www.example.com points to example.com/www/
dev.example.com points to example.com/dev/
Why don't I just have a branch called dev? Maybe I should... Advice?
(Anyway, it's nice to be able quickly, simultaneously open
corresponding files from both www & dev in textmate.
I guess I could do that with like git show master:www/index.html |
mate or something, but then it opens in a new textmate window. it's
just not the same. I guess there's always the possibility of editing
www/index.html when I actually want to be editing dev/index.html, but
then again, it's also possible to be editing the wrong branch.)
My .git/config file has the following aliases for deployment:
# deploy dev
ddev = !rsync -avi --copy-unsafe-links --exclude='*.DS_Store'
--delay-updates --delete-after --delete-excluded -e ssh
~/Sites/example.com/dev/ acani@acani.com:Sites/example.com/dev/
# deploy www
dpro = !rsync -avi --copy-unsafe-links --exclude='*.DS_Store'
--delay-updates --delete-after --delete-excluded -e ssh
~/Sites/example.com/www/ username@example.com:Sites/example.com/www/
Thanks!
Matt
next parent reply other threads:[~2010-02-07 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13f0168a1002061720t93ff6aew3420a41a547549d8@mail.gmail.com>
2010-02-07 2:05 ` Matt Di Pasquale [this message]
2010-02-07 4:40 ` how to apply patch? Tay Ray Chuan
2010-02-07 6:06 ` Matt Di Pasquale
2010-02-07 13:00 ` Tay Ray Chuan
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=13f0168a1002061805o5d64c05cy9d8f0190a8f37feb@mail.gmail.com \
--to=liveloveprosper@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.
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).