From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: OT: version control of .el files in NT Emacs
Date: Thu, 08 Sep 2016 23:02:40 +0530 [thread overview]
Message-ID: <87k2emxpon.fsf@gmail.com> (raw)
What's the best way to back up/version control my .Emacs and .el files
that are bog deep in some userprofile folder like
c:/Users/ADMIN/AppData/Roaming
I have git and cygwin installed. Ideally, I'd like to replicate the
changes into C:/Sivaram/repos everytime I tinker with the files in the
HOME.
I could do a shell script and cp the files over and add it to the
other repo but that's a drag and I'm likely to forget to do it
regularly.
sivaram
--
next reply other threads:[~2016-09-08 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 17:32 Sivaram Neelakantan [this message]
2016-09-08 20:05 ` OT: version control of .el files in NT Emacs John Mastro
2016-09-08 23:03 ` Óscar Fuentes
2016-09-09 4:50 ` Sivaram Neelakantan
2016-09-09 7:38 ` tomas
2016-09-09 14:53 ` Sivaram Neelakantan
2016-09-09 15:24 ` Óscar Fuentes
2016-09-10 4:57 ` Sivaram Neelakantan
2016-09-10 12:52 ` Óscar Fuentes
2016-09-10 14:04 ` Sivaram Neelakantan
2016-09-10 23:01 ` Óscar Fuentes
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2emxpon.fsf@gmail.com \
--to=nsivaram.net@gmail.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).