From: rhlee <richard@webdezign.co.uk>
To: git@vger.kernel.org
Subject: Re: Handling non-git config files
Date: Tue, 9 Mar 2010 02:50:27 -0800 (PST) [thread overview]
Message-ID: <1268131827388-4701369.post@n2.nabble.com> (raw)
In-Reply-To: <2cfc40321002241337q6b437803m82d05fb272cca6b2@mail.gmail.com>
Git-list,
Thanks to Jon, Ian and Tim for your replies.
I was reading Jon's reply and the workflow he uses seems to fit my purpose.
To migrate an application, you would branch it, set any local configuration
and commit. To bring over any changes you would just merge them over. This
would leave any deployment artifacts (a great term to describe local
changes) intact.
I have only been using branching and merging since November, when I was
instructed how to do so by git-list. I realise now that this is just basic
branching and merging. The workflow described will work with any SCM
software that supports branching and merging.
Richard
--
View this message in context: http://n2.nabble.com/Handling-non-git-config-files-tp4622419p4701369.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-03-09 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:37 Handling non-git config files Richard Lee
2010-02-24 1:46 ` Tim Mazid
2010-02-24 18:27 ` Ian Hobson
2010-02-24 21:37 ` Jon Seymour
2010-03-09 10:50 ` rhlee [this message]
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=1268131827388-4701369.post@n2.nabble.com \
--to=richard@webdezign.co.uk \
--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).