[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] empty commit
From: |
David Allouche |
Subject: |
Re: [Gnu-arch-users] empty commit |
Date: |
Tue, 22 Mar 2005 17:26:33 +0100 |
On Tue, 2005-03-22 at 10:27 -0500, Deliverable Mail wrote:
> Using bash, I run 'tla changes' with <up-arrow, enter> all the time.
> When I missed accidentally and hit enter on a 'tla commit -s
> "<note>"', it surprisingly commits again, although it was just run and
> no new changes were made. It still creates a "patch-<++N>" in {arch},
> which shows in now carefully typed 'tla changes'. How do I prevent
> such empty commits?
Short answer: you don't.
Longer answer: you may use a precommit hook or a wrapper that runs "tla
changes" to make sure there are actually changes before committing. But
that will significantly slow down committing.
Alternative solution: branch baz to prevent empty commits and provid a
"baz commit --empty-ok" option, I think such a patch would be welcome
there.
--
-- ddaa
signature.asc
Description: This is a digitally signed message part
- [Gnu-arch-users] Re: empty commit, (continued)
- Re: [Gnu-arch-users] Re: empty commit, David Allouche, 2005/03/22
- Re: [Gnu-arch-users] Re: empty commit, Tom Lord, 2005/03/22
- Re: [Gnu-arch-users] Re: empty commit, Tom Lord, 2005/03/22
- Re: [Gnu-arch-users] Re: empty commit, Mark A. Flacy, 2005/03/23
- Re: [Gnu-arch-users] Re: empty commit, Ulf Ochsenfahrt, 2005/03/24
- Re: [Gnu-arch-users] Re: empty commit, Tom Lord, 2005/03/24
- Re: [Gnu-arch-users] Re: empty commit, Adrian Irving-Beer, 2005/03/24
Re: [Gnu-arch-users] empty commit,
David Allouche <=