public inbox for sid-cvs@sourceware.org
help / color / mirror / Atom feed
From: bje@sources.redhat.com
To: sid-cvs@sources.redhat.com
Subject: src/sid/demos/voice-pager ChangeLog voice-page ...
Date: Wed, 02 Jan 2002 14:26:00 -0000	[thread overview]
Message-ID: <20020102222633.1178.qmail@sources.redhat.com> (raw)

CVSROOT:	/cvs/src
Module name:	src
Changes by:	bje@sources.redhat.com	2002-01-02 14:26:33

Modified files:
	sid/demos/voice-pager: ChangeLog voice-pager.tcl 

Log message:
	2002-01-03  Ben Elliston  <bje@redhat.com>
	
	* voice-pager.tcl: Update window title.

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/sid/demos/voice-pager/ChangeLog.diff?cvsroot=src&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/sid/demos/voice-pager/voice-pager.tcl.diff?cvsroot=src&r1=1.2&r2=1.3


             reply	other threads:[~2002-01-02 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 14:26 bje [this message]
2002-02-06 18:44 bje

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=20020102222633.1178.qmail@sources.redhat.com \
    --to=bje@sources.redhat.com \
    --cc=sid-cvs@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).