Re: Dumb "continuous" commit dumb question
- From
- David Tweed <david.tweed@gmail.com>
- Date
- Aug 19, 2008, 15:02 UTC
- Message-ID
- <e1dab3980808190802r202aadc0p2cf8431f645354e3@mail.gmail.com>
- In-Reply-To
- <32541b130808190754l43f053abnc4e3c5c064d6ade7@mail.gmail.com>
On Tue, Aug 19, 2008 at 3:54 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
> You could just have a makefile rule or bash alias that does something > like "make && git commit -a -m temp". Then remember to always run > that instead of 'make' when you're building.
As ever, I wanna do something more deviant than that :-) . The idea is to take a snapshot (if any tracked file has changed) roughly every ten minutes. If there happens to have been a successful compile around that time (+/- 1 minute say), grab the snapshot (including detecting potential newly created files) then. But if there hasn't, I still want a snapshot roughly on that 10 minute interval. I could try doing something like "git reset --soft HEAD~1 && git commit -a" if a make succeeds within 1 minute, on a strictly chronological snapshot but scripted resets make me a bit nervous.
It's not hyper-important, just something I'm thinking about.
-- cheers, dave tweed__________________________ david.tweed@gmail.com Rm 124, School of Systems Engineering, University of Reading. "while having code so boring anyone can maintain it, use Python." -- attempted insult seen on slashdot