From: "Carlos Martín Nieto" <cmn@elego.de>
To: "Rodrigo Cortés" <rcortes.ing@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Tracking database changes.
Date: Wed, 07 Sep 2011 00:18:09 +0200 [thread overview]
Message-ID: <1315347508.6080.4.camel@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <CAFSYZ5RjJYHByTMPu6LiM6awGitt3WqnVrLU34mA9t7O1MVHDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
On Tue, 2011-09-06 at 18:55 -0300, Rodrigo Cortés wrote:
> Is there a way to use git to track database changes?
That question is too generic to receive a useful answer. You could do a
nightly dump of the database contents and commit that file. Whether that
will give you anything useful is a different matter.
Cheers,
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-06 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 21:55 Tracking database changes Rodrigo Cortés
2011-09-06 22:18 ` Carlos Martín Nieto [this message]
[not found] <30328581.178675.1315346163453.JavaMail.trustmail@mail1.terreactive.ch>
2011-09-08 12:12 ` Victor Engmark
2011-09-08 12:16 ` Rodrigo Cortés
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=1315347508.6080.4.camel@centaur.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=rcortes.ing@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).