From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Welcome to sources.redhat.com
Date: Tue, 06 Aug 2002 11:55:00 -0000 [thread overview]
Message-ID: <20020806185528.GE4434@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3D501063.6020204@ecoscentric.com>
> If you don't mind, for the time being, if you write your own patches can
> you still submit them for approval by any other maintainer anyway rather
> than going ahead and checking it in and just posting the patch?
Should this be to ecos-patches or ecos-maintainers?
A while ago i posted to ecos-patches a patch for the ftp client. Here
is what i want to commit:
Index: ftpclient.c
===================================================================
RCS file: /cvs/ecos/ecos-opt/net/net/ftpclient/current/src/ftpclient.c,v
retrieving revision 1.4
diff -c -u -r1.4 ftpclient.c
--- ftpclient.c 23 May 2002 23:08:04 -0000 1.4
+++ ftpclient.c 6 Aug 2002 18:48:09 -0000
@@ -9,6 +9,7 @@
// -------------------------------------------
// This file is part of eCos, the Embedded Configurable Operating System.
// Copyright (C) 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
+// Copyright (C) 2002 Andrew Lunn.
//
// eCos is free software; you can redistribute it and/or modify it under
// the terms of the GNU General Public License as published by the Free
@@ -54,6 +55,7 @@
#include <network.h>
#include <stdio.h>
+#include <stdlib.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
@@ -128,7 +130,9 @@
char buf[BUFSIZ];
int more = 0;
int ret;
-
+ int first_line=1;
+ int code=0;
+
do {
if ((ret=get_line(s,buf,sizeof(buf),ftp_printf)) < 0) {
@@ -137,7 +141,19 @@
ftp_printf(0,"FTP: %s\n",buf);
- more = (buf[3] == '-');
+ if (first_line) {
+ code = strtoul(buf,NULL,0);
+ first_line=0;
+ more = (buf[3] == '-');
+ } else {
+ if (isdigit(buf[0]) && isdigit(buf[1]) && isdigit(buf[2]) &&
+ (code == strtoul(buf,NULL,0)) &&
+ buf[3]==' ') {
+ more=0;
+ } else {
+ more =1;
+ }
+ }
} while (more);
return (buf[0] - '0');
@@ -461,7 +477,7 @@
int ret;
- ret = command("QUIT","",s,msgbuf,msgbuflen,ftp_printf);
+ ret = command("QUIT",NULL,s,msgbuf,msgbuflen,ftp_printf);
if (ret < 0) {
return (ret);
}
next prev parent reply other threads:[~2002-08-06 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020806155646.18120.qmail@sources.redhat.com>
2002-08-06 11:07 ` Jonathan Larmour
2002-08-06 11:55 ` Andrew Lunn [this message]
2002-08-06 12:12 ` Gary Thomas
2002-08-06 12:17 ` Jonathan Larmour
2002-08-06 12:24 ` Gary Thomas
2002-08-06 12:33 ` Jonathan Larmour
2002-08-06 12:41 ` Gary Thomas
2002-08-06 14:53 ` Jonathan Larmour
2002-08-07 1:13 ` Andrew Lunn
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=20020806185528.GE4434@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@ecoscentric.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).