public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eric Brown" <ebrown@magbank.com>
To: <gentoo-dev@lists.gentoo.org>
Subject: RE: [gentoo-dev] Adding support to metadata.xml to mark longdescriptions as outdated
Date: Wed, 19 Oct 2005 16:21:54 -0400	[thread overview]
Message-ID: <4EF0C8957F24294E9933ED6B9DAEF3DB09A3AF@hurricane.magbank.com> (raw)

I think someone in the documentation herd (Xavier Neys?) has a system for this in place for regular documents, but it's probably not used for metadata files yet.

-----Original Message-----
From: Petteri Räty [mailto:betelgeuse@gentoo.org] 
Sent: Wednesday, October 19, 2005 3:59 PM
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Adding support to metadata.xml to mark longdescriptions as outdated

I thought that when I am bored I might translate the longdescriptions in
metadata.xml files to Finnish. While thinking about it the following
problem came to mind: When the English descriptions are updated there is
no way currently to mark the other translations as outdated. I think it
would be create to have a modified attribute or make an other solution
that would make it easy to find outdated descriptions in the tree. The
modification of the date could easily be integrated to for example repoman.

Regards,
Petteri Räty (Betelgeuse)


-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2005-10-19 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 20:21 Eric Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-19 19:58 [gentoo-dev] Adding support to metadata.xml to mark longdescriptions as outdated Petteri Räty
2005-10-19 21:04 ` Flammie Pirinen
2005-10-19 21:19   ` Petteri Räty
2005-10-19 22:20     ` Flammie Pirinen

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=4EF0C8957F24294E9933ED6B9DAEF3DB09A3AF@hurricane.magbank.com \
    --to=ebrown@magbank.com \
    --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