From: "David Tweed" <david.tweed@gmail.com>
To: "Andy Parkins" <andyparkins@gmail.com>
Cc: git@vger.kernel.org, "Tom Schinckel" <gunny01@gmail.com>,
"David Kågedal" <davidk@lysator.liu.se>
Subject: Re: Git Questions
Date: Mon, 20 Aug 2007 13:59:41 +0100 [thread overview]
Message-ID: <e1dab3980708200559v3f1def4ft85e31afb08394790@mail.gmail.com> (raw)
In-Reply-To: <200708201346.21557.andyparkins@gmail.com>
> On Monday 2007 August 20, Tom Schinckel wrote:
>
> > The reason I want to do that is so I can set up blind commits that I can
> > add in a anacron job or something. The information about the files isn't
> > really important
Regarding your basic intention, I've worked on something _similar_
using git and put it up on the web (although not got around to editing
the git wiki) at
http://www.personal.rdg.ac.uk/~sis05dst/chronoversion.htm
(with a minor update is going to go up when 1.5.3 gets released & I
test it works.) There are two important differences with what you want
to do:
1. As I recall someone else saying when talking about using SCM
on their home directory (Joey Hess?), if you blanket record
everything you then end up being careful about, eg, piping a
grep search into a temporary file for some purpose, etc. So
chronoversion takes a python function that decides if a file
is "worth recording" (which can be by suffix or more general
analysis).
2. As I've got a nervous tick of saving every couple of minutes
(in case the editor or network I'm on dies), recording on save
is too fine a granularity for me, so the script is designed to
run from a cron job (I have it at once an hour) and not make
a commit if it finds nothing has changed.
As I say, not exactly what you're looking for but it might be
in the right direction.
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"we had no idea that when we added templates we were adding a Turing-
complete compile-time language." -- C++ standardisation committee
next prev parent reply other threads:[~2007-08-20 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 9:55 Git Questions Tom Schinckel
2007-08-20 10:06 ` Jeff King
2007-08-20 11:23 ` David Kågedal
2007-08-20 12:15 ` Tom Schinckel
2007-08-20 12:46 ` Andy Parkins
2007-08-20 12:59 ` David Tweed [this message]
2007-08-20 18:35 ` Jan Hudec
2007-08-20 12:53 ` Matthieu Moy
2007-08-20 13:06 ` David Tweed
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=e1dab3980708200559v3f1def4ft85e31afb08394790@mail.gmail.com \
--to=david.tweed@gmail.com \
--cc=andyparkins@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=gunny01@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).