[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Git commit messages
- From: Alex Blewitt <alex.blewitt@xxxxxxxxx>
- Date: Wed, 22 Jun 2011 16:36:06 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=ToGhkXfGHJ9bkqUdzpm+JtPZHfrpeXHYymprgX101fQQHMxYQOAPG1XCchPvbMGVQy MUDjdgbfD7Wkj97BN9OlqCIdcFjImmIHoi1JpbFAjjwXgxzeqG4lbX1V/EQ7ThwRofFi WU0U9JFJoSQ7WDuUMTZQg9VdGICYC92yc1syo=
On 22 Jun 2011, at 15:44, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
> The problem is that you don't exactly know when the change is done and therefore have to type the same message over and over again in multiple commits.
The time when you know it's done is at the end. So only type the detailed message in there.
For other work in progress messages you can either leave the message blank or trivial and do "commit amends" to update the commit as you go, or do a rebase/squash to condense them down into a single message prior to pushing to the remote repository.
The issue isn't that every commit needs a detailed message, but that commits pushed to the remote repo do need them. Much like you would do a bunch of work and then attach a patch in bugzilla - the interim work needn't be of high quality but the patch submitted should be (and have more detail than "fixes bug")