As it sounds like you're versioning your home directory you might also
want to take a look at VCSH <https://github.com/RichiH/vcsh>. I first heard
of it on the GitMinutes podcast which Thomas Ferris Nicolaisen (a previous
commenter on this thread) presents. I'm not sure how well it fits with what
you want to do but it might be useful so I thought I'd mention it.
On Friday, 2 August 2013 22:12:36 UTC+1, Dale Worley wrote:
> > Does http://www.emacswiki.org/emacs/Git do what you want?
> No, nothing I found listed there seemed to be really helpful.
> > ...Apologies if you already know what I discuss below but I just thought
> > I'd put it here just in case it helps...
> > So if I understand your scenario correctly you'd probably want to...
> > 1. Clone your home repo somehwere else.
> > 2. Go through this history, checking out commits, etc. in this other
> > repo to find the version of the file(s) you want.
> > 3. Create a branch (or possibly do it on master), merge, reset, etc.
> > files to get the files looking as you want them to be.
> > 4. (if you created a branch to work on) Merge the branch back into
> > master.
> > 5. Push that master back to your home directory.
> My environment is strange, in that the commits are generated by a cron
> job, so their commit messages are all the same. However, their dates
> are useful labels.
> I don't want to have to clone the repository, and I really shouldn't
> have to, because the tool would be doing essentially read-only access.
> I'm not concerned with checking out commits or making branches.
> Instead, I'd like to *look* at the versions of a file. If it was
> integrated in Emacs, the various versions would be put into various
> Emacs buffers. From those buffers, I'd pick the files or parts of
> files I wanted, and store them to disk wherever I want to. (This may
> not seem very clear, but if you've used Emacs, you'll know the idiom
> it uses for this sort of task.)
> I'm not concerned with an organized method of "pushing the master back
> to my home directory", because once I revise the files as I want them,
> the cron job will record those changes. (Of course, the Git history
> won't document where those changes really came from. But this is a
> continuous-backup system, not a real version control system.)
> It turns out that qgit does most of what I need. The perfect system
> would be essentially a reimplementation of qgit as an Emacs mode (in
> the same way that Emacs allows me to look into a Zip file, and all the
> files saved in it, as if it was an ordinary directory).
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.