all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Cc: Sivaram Neelakantan <nsivaram.net@gmail.com>
Subject: Re: OT: version control of .el files in NT Emacs
Date: Thu, 8 Sep 2016 13:05:33 -0700	[thread overview]
Message-ID: <CAOj2CQQboPk7GH-cFRBz30u09egMukZ2=pCU4UZRNwju2TeFAQ@mail.gmail.com> (raw)
In-Reply-To: <87k2emxpon.fsf@gmail.com>

Sivaram Neelakantan <nsivaram.net@gmail.com> wrote:
>
> 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.

Why not work with the files in the repos themselves? In other words, do
they really need to be in two different places?

If c:/Users/ADMIN isn't an appropriate place to keep a git repository,
you could override HOME to e.g. c:/Sivaram, and then create
c:/Sivaram/.emacs.d as a git repository.

        John



  reply	other threads:[~2016-09-08 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 17:32 OT: version control of .el files in NT Emacs Sivaram Neelakantan
2016-09-08 20:05 ` John Mastro [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOj2CQQboPk7GH-cFRBz30u09egMukZ2=pCU4UZRNwju2TeFAQ@mail.gmail.com' \
    --to=john.b.mastro@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nsivaram.net@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.