Re: Dumb "continuous" commit dumb question
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Aug 19, 2008, 14:54 UTC
- Message-ID
- <32541b130808190754l43f053abnc4e3c5c064d6ade7@mail.gmail.com>
- In-Reply-To
- <e1dab3980808190732i303f06ach50e36e13a624bd23@mail.gmail.com>
On Tue, Aug 19, 2008 at 10:32 AM, David Tweed <david.tweed@gmail.com> wrote:
Show 6 quoted lines
> One problem with chronological backups is that they often don't > compile/run so you can't bisect on them. One thing I have been trying > to figure out is if there's an easy way to modify my build system so > that it makes a commit approximately every 10 minutes but just after a > successful compile. However, that looks to be a bit too complex and > error prone for the moment.
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.
Of course, committing on a side branch and not screwing with the index would be much less intrusive.
Avery