From: Dave Nellans <dnellans@cs.utah.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] dev's updating changlogs
Date: 16 Apr 2003 18:21:57 -0600 [thread overview]
Message-ID: <1050538917.7371.12.camel@malfus> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
sorry to harp on this but after an emerge sync this afternoon
openoffice-bin wanted to upgrade to 1.1_beta after it has already been
upgraded once, then downgraded to 1.0.3. yet in the Changelog there is
still NO entry past 1.0.2 from late january.
could devleopers PLEASE follow the procedure and update the changlogs?
while i appriciate the ebuild work, its quite annoying to see major
upgrades like this with zero documentation about it explaining why its
bouncing back and forth between versions...
sorry for a bit of rant but i think its important to update the
Changelogs so mere users of the package know why they're playing the
upgrade/downgrade game constantly!
dave
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-16 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 0:21 Dave Nellans [this message]
2003-04-17 0:15 ` [gentoo-dev] dev's updating changlogs Seth Chandler
2003-04-17 0:58 ` Dave Nellans
2003-04-17 2:32 ` Peter Ruskin
2003-04-17 7:04 ` Dave Nellans
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=1050538917.7371.12.camel@malfus \
--to=dnellans@cs.utah.edu \
--cc=gentoo-dev@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