diff -ur linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-sparc/fbio.h
linux-kernel-headers-2.5.999-test7-bk/include/asm-sparc/fbio.h
--- linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-sparc/fbio.h
2003-10-15 11:10:33.0 -0400
+++ linux-kernel-headers-2.5.999-test7-bk/include
diff -ur linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-sparc/fbio.h
linux-kernel-headers-2.5.999-test7-bk/include/asm-sparc/fbio.h
--- linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-sparc/fbio.h 2003-10-15
11:10:33.0 -0400
+++ linux-kernel-headers-2.5.999-test7-bk/include
On Thu, Oct 23, 2003 at 11:10:55AM +0900, GOTO Masanori wrote:
> At Wed, 22 Oct 2003 11:24:19 -0400,
> Daniel Jacobowitz wrote:
> > Currently, the default locale setting for the system can be accessed
> > only through /etc/environment, which is a configuration file for PAM.
> > Setting the locale
On Thu, Oct 23, 2003 at 11:10:55AM +0900, GOTO Masanori wrote:
> At Wed, 22 Oct 2003 11:24:19 -0400,
> Daniel Jacobowitz wrote:
> > Currently, the default locale setting for the system can be accessed
> > only through /etc/environment, which is a configuration file for PAM.
> > Setting the locale
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225466: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#224744: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223769: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220983: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220693: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#222886: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218131: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218717: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219839: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221317: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223891: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223891: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225466: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225601: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:27 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#226688: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Accepted:
glibc-doc_2.3.2.ds1-11_all.deb
to pool/main/g/glibc/glibc-doc_2.3.2.ds1-11_all.deb
glibc_2.3.2.ds1-11.diff.gz
to pool/main/g/glibc/glibc_2.3.2.ds1-11.diff.gz
glibc_2.3.2.ds1-11.dsc
to pool/main/g/glibc/glibc_2.3.2.ds1-11.dsc
libc-udeb_2.3.2.ds1-11_i386.udeb
to pool/main/g/glibc/l
glibc_2.3.2.ds1-11_i386.changes uploaded successfully to localhost
along with the files:
glibc_2.3.2.ds1-11.dsc
glibc_2.3.2.ds1-11.diff.gz
glibc-doc_2.3.2.ds1-11_all.deb
locales_2.3.2.ds1-11_all.deb
libc6_2.3.2.ds1-11_i386.deb
libc6-dev_2.3.2.ds1-11_i386.deb
libc6-dbg_2.3.2.ds1-11_i38
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225466: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#224744: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223769: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220983: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220693: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#222886: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218131: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218717: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219839: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221317: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223891: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#223891: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225466: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:26 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225601: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 20 Jan 2004 16:50:27 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#226688: fixed in glibc 2.3.2.ds1-11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Accepted:
glibc-doc_2.3.2.ds1-11_all.deb
to pool/main/g/glibc/glibc-doc_2.3.2.ds1-11_all.deb
glibc_2.3.2.ds1-11.diff.gz
to pool/main/g/glibc/glibc_2.3.2.ds1-11.diff.gz
glibc_2.3.2.ds1-11.dsc
to pool/main/g/glibc/glibc_2.3.2.ds1-11.dsc
libc-udeb_2.3.2.ds1-11_i386.udeb
to pool/main/g/glibc/l
glibc_2.3.2.ds1-11_i386.changes uploaded successfully to localhost
along with the files:
glibc_2.3.2.ds1-11.dsc
glibc_2.3.2.ds1-11.diff.gz
glibc-doc_2.3.2.ds1-11_all.deb
locales_2.3.2.ds1-11_all.deb
libc6_2.3.2.ds1-11_i386.deb
libc6-dev_2.3.2.ds1-11_i386.deb
libc6-dbg_2.3.2.ds1-11_i38
On Fri, 16 Jan 2004, GOTO Masanori wrote:
> At Thu, 20 Nov 2003 23:09:27 +0200 (EET),
> Martin-Éric Racine wrote:
> > > That said, I believe I upgraded it to something in the 2.3.2.ds1 series at
> > > one point while still running 2.4 without obvious problems.
> >
> > IIRC 2.3.2 up to ds1-8 worke
On Tue, Jan 20, 2004 at 12:18:30PM +0300, Vladimir Prus wrote:
> Daniel Jacobowitz wrote:
>
> > > > > >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> > > > > >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> > > >
> > > > What is this trying to accomplish? You're going
免费赠送百万邮箱地址和白款群发软件！！条件只有一个在你的网站给我的网站做一个友情连接！！！
联系QQ：121334033 联系邮箱:[EMAIL PROTECTED]
Email营销：未来最火的网络营销方式
电子邮件营销？您可能有点陌生，但作为爱上网的您肯定碰到过这样的事儿--是不是曾在自己的邮箱
中发现一封来自某某公司的邮件？里面的内容多半是说该公司的商品开始打折；该公司邀请您免费成
为会员，赠送小礼品……这些做广告的公司给您寄电子邮件推销商品及服务的过程就叫"电子邮件营销"。
与电话推销、邮寄推销信等传统的营销方法相比，现代网络化工具电子邮件已逐渐开始体现出
On Fri, 16 Jan 2004, GOTO Masanori wrote:
> At Thu, 20 Nov 2003 23:09:27 +0200 (EET),
> Martin-Éric Racine wrote:
> > > That said, I believe I upgraded it to something in the 2.3.2.ds1 series at
> > > one point while still running 2.4 without obvious problems.
> >
> > IIRC 2.3.2 up to ds1-8 worke
On Tue, Jan 20, 2004 at 12:18:30PM +0300, Vladimir Prus wrote:
> Daniel Jacobowitz wrote:
>
> > > > > >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> > > > > >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> > > >
> > > > What is this trying to accomplish? You're going
免费赠送百万邮箱地址和白款群发软件！！条件只有一个在你的网站给我的网站做一个友情连接！！！
联系QQ：121334033 联系邮箱:[EMAIL PROTECTED]
Email营销：未来最火的网络营销方式
电子邮件营销？您可能有点陌生，但作为爱上网的您肯定碰到过这样的事儿--是不是曾在自己的邮箱
中发现一封来自某某公司的邮件？里面的内容多半是说该公司的商品开始打折；该公司邀请您免费成
为会员，赠送小礼品……这些做广告的公司给您寄电子邮件推销商品及服务的过程就叫"电子邮件营销"。
与电话推销、邮寄推销信等传统的营销方法相比，现代网络化工具电子邮件已逐渐开始体现出
Repository: glibc-package/debian/po
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:nl.po pt_BR.po
Repository: glibc-package/debian
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:changelog
Repository: glibc-package/debian/debhelper.in
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:libc.preinst
Repository: glibc-package/debian/po
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:nl.po pt_BR.po
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
Repository: glibc-package/debian
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
Repository: glibc-package/debian/debhelper.in
who:dan
time: Tue Jan 20 07:42:24 MST 2004
Log Message:
Quote a backslash in libc.preinst
(and regenerate PO files...)
Files:
changed:libc.preinst
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+c2Nl
bnQgPGJyPg0KPGJyPg0Kb2YgdmljdG9yeTxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3dy4x
Mmhlbi5
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+c2Nl
bnQgPGJyPg0KPGJyPg0Kb2YgdmljdG9yeTxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3dy4x
Mmhlbi5
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+b25j
ZTxicj4NCmEgbG9uZyB0aW1lIGFnbzxicj4NCjxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3
dy4xMmh
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+c2Nl
bnQgPGJyPg0KPGJyPg0Kb2YgdmljdG9yeTxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3dy4x
Mmhlbi5
Daniel Jacobowitz wrote:
> > > > >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> > > > >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> > >
> > > What is this trying to accomplish? You're going to get shared
> > > versions of some libraries and dynamic versions of oth
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+c2Nl
bnQgPGJyPg0KPGJyPg0Kb2YgdmljdG9yeTxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3dy4x
Mmhlbi5
PGJyPjxicj4NCjxjZW50ZXI+PGEgaHJlZj0iaHR0cDovL3d3dy4xMmhlbi5pbmZvL2FscGhh
Lz9idXN0ZXIiPlRoaXMgZmFudGFzdGljIHN1cHBsZW1lbnQ8YnI+aGFzIG1hZGUgbWFsZSAg
c3RhcnMgZmFtb3VzPGJyPiBDbGljayBoZXJlPC9hPjxicj48YnI+PGJyPg0KDQo8YnI+b25j
ZTxicj4NCmEgbG9uZyB0aW1lIGFnbzxicj4NCjxicj4NCg0KPGEgaHJlZj0iaHR0cDovL3d3
dy4xMmh
Daniel Jacobowitz wrote:
> > > > >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> > > > >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> > >
> > > What is this trying to accomplish? You're going to get shared
> > > versions of some libraries and dynamic versions of oth
58 matches
Mail list logo
