From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCH v2 17/19] ebuild-writing/misc-files: remove ChangeLog section #485314
Date: Wed, 27 Jan 2016 08:12:47 +0100 [thread overview]
Message-ID: <22184.28143.866612.695096@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <56A84544.6010207@binghamton.edu>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
>>>>> On Tue, 26 Jan 2016, Göktürk Yüksek wrote:
> Ulrich Mueller:
>> The devmanual is the one central place where our development
>> workflow should be documented, not some random wiki page.
>>
> If the most up-to-date information is on the wiki, constantly
> updating devmanual to match the wiki creates unnecessary maintenance
> burden.
The point is that any information that constitutes policy should be
traceable, e.g. there should be a bug or a patch should be posted to
the mailing lists.
> Related to my point above, looks like the git workflow is still in
> the process of making. I expect that some discussion will continue
> to take place in the future. We can always fix the other parts of
> the devmanual and come back to this.
I beg to differ. Apart from some small details, things have settled.
Looking at the history of the wiki page, there was quite some activity
in the two months following the switch to git, but very little after.
> Is it possible to merge this changeset as is while the workflow
> matures, or should I go for a round 3?
I'd prefer a round 3, including Michael's suggestions at least. That
is, include the "Commit message format" subsection from the wiki page
(or even the "Commit policy" section; it is not much longer).
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2016-01-27 7:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 8:45 [gentoo-dev] [PATCH v2 00/19] devmanual: update the docs for post git-migration Gokturk Yuksek
2016-01-24 8:45 ` [gentoo-dev] [PATCH v2 01/19] general-concepts/manifest: drop the use of "CVS keyword expansion" #558642 Gokturk Yuksek
2016-01-24 8:45 ` [gentoo-dev] [PATCH v2 02/19] general-concepts/mirrors: substitute "CVS" with "the git tree" #558642 Gokturk Yuksek
2016-01-24 8:45 ` [gentoo-dev] [PATCH v2 03/19] general-concepts/tree: substitute "CVS" with "git" #558642 Gokturk Yuksek
2016-01-24 8:45 ` [gentoo-dev] [PATCH v2 04/19] general-concepts/tree: replace the mention of ChangeLog #558642 Gokturk Yuksek
2016-01-24 8:45 ` [gentoo-dev] [PATCH v2 05/19] ebuild-writing/misc-files: replace the code for cvs commit with git #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 06/19] ebuild-writing/user-submitted: do not put user information in ChangeLog #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 07/19] appendices/editor-configuration/emacs: remove the CVS related setting #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 08/19] ebuild-maintenance: rewrite the text on adding binary files to the tree #558642 Gokturk Yuksek
2016-01-24 15:00 ` Patrice Clement
2016-01-24 15:29 ` [gentoo-dev] " Duncan
2016-01-24 15:44 ` [gentoo-dev] " Andrew Savchenko
2016-01-24 23:44 ` Göktürk Yüksek
2016-01-25 0:51 ` Brian Dolbec
2016-01-24 16:38 ` Göktürk Yüksek
2016-01-24 17:17 ` James Le Cuirot
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 09/19] ebuild-maintenance: rewrite the subsection on commit policy for git #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 10/19] ebuild-maintenance: rewrite the subsection on upgrading ebuilds " Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 11/19] ebuild-maintenance: rewrite the subsection on moving " Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 12/19] ebuild-maintenance: rewrite the subsection on removing " Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 13/19] ebuild-maintenance: rewrite the subsection on removing packages " Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 14/19] ebuild-maintenance: replace "cvs commit" with "git commit" #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 15/19] general-concepts/git-to-rsync/diagram: update the description for git #558642 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 16/19] " Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 17/19] ebuild-writing/misc-files: remove ChangeLog section #485314 Gokturk Yuksek
2016-01-25 0:43 ` [gentoo-dev] " Ulrich Mueller
2016-01-25 1:02 ` Göktürk Yüksek
2016-01-25 1:13 ` Michael Orlitzky
2016-01-25 8:17 ` Ulrich Mueller
2016-01-27 4:19 ` Göktürk Yüksek
2016-01-27 7:12 ` Ulrich Mueller [this message]
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 18/19] tools-reference: remove the echangelog page #485314 Gokturk Yuksek
2016-01-24 8:46 ` [gentoo-dev] [PATCH v2 19/19] general-concepts/tree: remove the reference to the ChangeLog #485314 Gokturk Yuksek
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=22184.28143.866612.695096@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox