From: "Gerrit P. Haase" <gerrit@familiehaase.de>
To: cygwin@cygwin.com
Subject: Re: rebaseall (was Re: Perl Win32::Shortcut screws up fork)
Date: Sat, 16 Jul 2005 00:32:00 -0000 [thread overview]
Message-ID: <42D85585.4070206@familiehaase.de> (raw)
In-Reply-To: <20050715205940.GA2856@tishler.net>
Jason Tishler wrote:
> On Fri, Jul 15, 2005 at 01:21:11PM +0100, Dave Korn wrote:
>
>>----Original Message----
>>
>>>From: Jason Tishler
>>>Sent: 15 July 2005 12:27
>>
>>>Exactly! Right after my previous post, I started to investigate
>>>enhancing rebase to support rebaseall functionality. I quickly
>>>realized that this change would not require too much effort.
>>
>> Reading the .gz files will probably be the worst bit of it!
>
>
> Actually, the above was much easier than I thought. I came up with the
> following test program in just a few minutes:
>
> #include <stdio.h>
> #include <string.h>
> #include <zlib.h>
>
> int
> main(int argc, const char* argv[])
> {
> const char* filename = argv[1];
> const char* mode = "rb";
> const int size = 1024;
> char buffer[size];
>
> gzFile file = gzopen(filename, mode);
> while (gzgets(file, buffer, size) > 0)
> {
> int length = strlen(buffer);
> if (buffer[length - 1] == '\n')
> buffer[length - 1] = '\0';
> puts(buffer);
> }
> gzclose(file);
> }
Cool! You're the best ;)
$ ./readgz /etc/setup/bc.lst.gz
usr/
usr/bin/
usr/bin/bc.exe
usr/bin/dc.exe
usr/share/
usr/share/info/
usr/share/info/bc.info
usr/share/info/dc.info
usr/share/man/
usr/share/man/man1/
usr/share/man/man1/bc.1
usr/share/man/man1/dc.1
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-07-16 0:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 19:06 Perl Win32::Shortcut screws up fork Adye, TJ (Tim)
[not found] ` <7231C15EAC2F164CA6DC326D97493C8BA1C3FA@exchange35.fed.cclr c.ac.uk>
2005-07-08 0:12 ` Larry Hall
2005-07-08 1:11 ` Brian Dessent
2005-07-08 1:19 ` Christopher Faylor
2005-07-08 1:40 ` Brian Dessent
2005-07-08 2:05 ` Eric Blake
2005-07-08 2:27 ` Brian Dessent
2005-07-08 2:38 ` Eric Blake
2005-07-08 2:54 ` Brian Dessent
2005-07-08 2:06 ` Christopher Faylor
2005-07-08 2:21 ` Igor Pechtchanski
2005-07-08 3:45 ` Christopher Faylor
2005-07-08 2:24 ` Eric Blake
2005-07-08 3:50 ` Christopher Faylor
2005-07-08 9:48 ` Gerrit P. Haase
2005-07-11 12:45 ` Jason Tishler
2005-07-12 2:08 ` Christopher Faylor
2005-07-14 12:23 ` rebaseall (was Re: Perl Win32::Shortcut screws up fork) Jason Tishler
2005-07-14 13:12 ` Dave Korn
2005-07-14 14:06 ` Brian Dessent
2005-07-14 19:57 ` Christopher Faylor
2005-07-14 14:41 ` Dave Korn
2005-07-14 15:02 ` Gerrit P. Haase
2005-07-14 15:28 ` Dave Korn
2005-07-14 15:58 ` Gerrit P. Haase
2005-07-14 16:09 ` Dave Korn
2005-07-14 15:58 ` Dave Korn
2005-07-14 20:01 ` Christopher Faylor
2005-07-15 11:29 ` Jason Tishler
2005-07-15 12:22 ` Dave Korn
2005-07-15 21:01 ` Jason Tishler
2005-07-16 0:32 ` Gerrit P. Haase [this message]
2005-07-18 13:00 ` Dave Korn
2005-07-15 14:18 ` Christopher Faylor
2005-07-16 19:08 ` Jason Tishler
2005-07-08 1:35 ` Perl Win32::Shortcut screws up fork Eric Blake
2005-07-08 2:27 ` Brian Dessent
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=42D85585.4070206@familiehaase.de \
--to=gerrit@familiehaase.de \
--cc=cygwin@cygwin.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).