All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tanous, Ed" <ed.tanous@intel.com>
To: 'Alexander Amelkin' <a.amelkin@yadro.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: RE: Proposals for commit log policy
Date: Wed, 22 Aug 2018 20:39:50 +0000	[thread overview]
Message-ID: <7E9441B1E5EFFD4681F54958E82169934583385B@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <0ef9181f-eb70-552b-3411-da2bc9676be1@yadro.com>

I'm not really understanding the issue here.  Is the log information not available in the individual repositories?  Is it just hard to parse?  Could this be automated, either using a script, or a list of repositories?

While I think there's value in the logs, I don't think maintainers time is best used by creating git logs manually all the time, especially when it should be easy enough to parse the git logs between the recipe bumps.  I've had to do this before to do bisects before, and it's not too difficult once you get the hang of it.

I really do appreciate you generating a real set of release notes, and I want to make it easy, I'd just prefer if we as a project didn't move work onto the individual developers to make it happen.

-Ed

  parent reply	other threads:[~2018-08-22 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 12:29 Proposals for commit log policy Alexander Amelkin
2018-08-22 15:01 ` Gunnar Mills
2018-08-23  8:23   ` Alexander Amelkin
2018-08-22 20:39 ` Tanous, Ed [this message]
2018-08-23  8:44   ` Alexander Amelkin
2018-08-28 22:40     ` Tanous, Ed
2018-08-22 23:58 ` Joel Stanley
2018-08-28 10:29   ` Brad Bishop
2018-08-28 15:43     ` Andrew Geissler
2018-08-28 16:13       ` Patrick Venture
2018-08-28 17:44       ` Gunnar Mills
2018-08-28 22:20         ` Tanous, Ed
2018-08-28 22:43           ` Kun Yi
2018-09-04 20:20           ` Brad Bishop
2018-09-04 23:38             ` Patrick Venture
2018-09-06 13:13               ` Alexander Amelkin

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=7E9441B1E5EFFD4681F54958E82169934583385B@ORSMSX114.amr.corp.intel.com \
    --to=ed.tanous@intel.com \
    --cc=a.amelkin@yadro.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.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.