From: Yasushi SHOJI <yashi@atmark-techno.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb - Use <description> instead of <content:encoded>.
Date: Fri, 19 Aug 2005 01:52:19 +0900 [thread overview]
Message-ID: <87fyt7w5ks.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <20050818153607.GX11882MdfPADPa@garage.linux.student.kuleuven.ac.be>
At Thu, 18 Aug 2005 17:36:07 +0200,
Sven Verdoolaege wrote:
>
> On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote:
> > Use <description> instead of <content:encoded>.
> >
>
> Hmm.... in snownews this gets displayed as "Use instead of .".
> (http://www.liacs.nl/~sverdool/gitweb.cgi?p=gitweb.git;a=rss)
>
> Is that a problem with snownews or with gitweb ?
we are not sure. As Kay said, we need to find out _authoritative_
information for this.
regards,
--
yashi
next prev parent reply other threads:[~2005-08-18 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 14:30 [PATCH] gitweb - Use <description> instead of <content:encoded> Yasushi SHOJI
2005-08-18 15:36 ` Sven Verdoolaege
2005-08-18 16:52 ` Yasushi SHOJI [this message]
2005-08-18 16:01 ` Kay Sievers
2005-08-18 16:26 ` Yasushi SHOJI
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=87fyt7w5ks.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).