All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM 2010: [RFC] useful commit message
Date: Mon, 01 Nov 2010 15:36:40 -0400	[thread overview]
Message-ID: <20101101193640.GE11514@denix.org> (raw)
In-Reply-To: <iajftl$ek9$1@dough.gmane.org>

On Sun, Oct 31, 2010 at 11:20:36AM +0100, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 29-10-10 11:02, Paul Menzel wrote:
> > Dear OE folks,
> > 
> > 
> > could you please discuss the following proposal.
> > 
> > I would very much like more elaborate commit messages. This is in my
> > opinion already demanded by the commit policy [1], but often patch
> > submitters, especially those not sending changes to review to the list,
> > since they have direct access to the repository, fail to adhere to the
> > policy.
> > 
> > The reason is, quite often I do not understand why a change was
> > necessary. It would very much help me, if at least the error message was
> > pasted to be able to compare with one???s own error messages and what
> > distribution and machine was used to test the recipe.
> 
> We discussed this at OEDEM and AIUI the TSC will make a recommendation
> about it later, but in the meantime you can expand existing commit
> messages with git notes:

While git-notes is relatively new (1.6.6+), it's a very useful feature. Some 
more details here:

http://progit.org/2010/08/25/notes.html

-- 
Denys

> 
> - -----------------
> GIT-NOTES(1)
> 
> NAME
>        git-notes - Add/inspect commit notes
> 
> SYNOPSIS
>        git notes (edit [-F <file> | -m <msg>] | show) [commit]
> 
> DESCRIPTION
>        This command allows you to add notes to commit messages, without
> changing the commit. To discern these notes from the message stored in
> the commit object, the notes
>        are indented like the message, after an unindented line saying
> "Notes:".
> 
>        To disable commit notes, you have to set the config variable
> core.notesRef to the empty string. Alternatively, you can set it to a
> different ref, something like
>        "refs/notes/bugzilla". This setting can be overridden by the
> environment variable "GIT_NOTES_REF".
> 
> SUBCOMMANDS
>        edit
>            Edit the notes for a given commit (defaults to HEAD).
> 
>        show
>            Show the notes for a given commit (defaults to HEAD).
> 
> OPTIONS
>        -m <msg>
>            Use the given note message (instead of prompting). If
> multiple -m (or -F) options are given, their values are concatenated as
> separate paragraphs.
> 
>        -F <file>
>            Take the note message from the given file. Use - to read the
> note message from the standard input. If multiple -F (or -m) options are
> given, their values are
>            concatenated as separate paragraphs.
> - -----------------
> 
> It would of course be better to get it right the first time :)
> 
> regards,
> 
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> 
> iD8DBQFMzUL0MkyGM64RGpERAlfMAJsGBzO3oZ68BEvCK0QehPsvbnB4hQCgpp4d
> sj+pB/5JTY1O7NJtuyMvsyU=
> =DiG8
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



      reply	other threads:[~2010-11-01 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29  9:02 OEDEM 2010: [RFC] useful commit message Paul Menzel
2010-10-29 10:45 ` Frans Meulenbroeks
2010-10-31 10:20 ` Koen Kooi
2010-11-01 19:36   ` Denys Dmytriyenko [this message]

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=20101101193640.GE11514@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.