public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dylan Carlson <absinthe@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] changelogs...
Date: Thu, 22 May 2003 17:56:19 -0400	[thread overview]
Message-ID: <200305221756.38366.absinthe@gentoo.org> (raw)
In-Reply-To: <1053636678.1242.23.camel@mermaid.isi.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu May 22 2003 4:51 pm, Spundun Bhatt wrote:
> As a sidenote to the currently going discussion about package
> description.
>
> When I recieve updates of ebuilds... I am usually curious whats new to
> checkout (I am sure everybody is).
> I always do emerge -u --deep world -p --changelog
> But more often than not... chang log says "version bump" which doesnt
> tellme anything.
> Is it feasible to add a url to the release note of the release (in cases
> where its not an ebuild bugfix release).
> I dont know if there anything to do about it.. but I see gnome.org as
> the homepage of all components so its not easy atall to find out what a
> perticular component does.

I think that would be a needless expenditure of bits.   There is always 
HOMEPAGE set in the ebuild for people to query, and that's where people 
should go to get release information.  

If no information is available about the release on the HOMEPAGE, then I 
agree some notes in the ChangeLog would be appropriate.

Cheers,
Dylan Carlson

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+zUeVPQS8wXCOFl8RAhKuAJ0eAImHazoFHbJHcOXe/z9S4jrIHgCfSyEC
jgImkiUL6eZPgtNkl5NHLEk=
=lJM9
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-22 21:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 20:51 [gentoo-dev] changelogs Spundun Bhatt
2003-05-22 21:56 ` Dylan Carlson [this message]
2003-05-22 21:58   ` Spundun Bhatt
2003-05-22 22:02     ` Spundun Bhatt
2003-05-23  0:36       ` foser
2003-05-23 10:29         ` Sven Vermeulen
2003-05-23  0:41     ` foser
  -- strict thread matches above, loose matches on Subject: below --
2005-07-27  2:05 [gentoo-dev] Changelogs Alec Warner
2005-07-27  2:22 ` Georgi Georgiev
2005-07-27 14:50 ` Jason Stubbs
2005-07-28  0:02   ` Alec Warner
2005-07-28 13:58     ` Jason Stubbs
2005-07-27 16:59 ` Maurice van der Pot
2005-07-27 18:23   ` Alec Joseph Warner
2005-07-27 18:29     ` Donnie Berkholz
2003-05-22 22:31 [gentoo-dev] changelogs Rex Young
2003-05-23  6:49 ` Dylan Carlson
2001-11-05 11:26 Jon Nelson
2001-11-05 11:37 ` Grant Goodyear
2001-11-05 12:12   ` Jon Nelson

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=200305221756.38366.absinthe@gentoo.org \
    --to=absinthe@gentoo.org \
    --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