Cygpath patch resend

it -P|--smprogramsoutput Start Menu `Programs' directory and exit I've also fixed the issue where options that depend on other options do not behave as expected. For example, -Ww and -wW behaved differently but now will do the right thing. Here's a changelog: 2001-01-16 Joshu

New file for winsup/utils

FAQs, websites, etc. Changelog: 2001-02-20 Joshua Daniel Franklin <[EMAIL PROTECTED]> * mkshortcut.c: new file, utility to create shortcuts from scripts * utils.sgml: updated to include mkshortcut --- Robert Collins <[EMAIL PROTECTED]> wrote: > > === > - Origin

version information for cygcheck

specified usage will be output to stdout instead of stderr, which is more standard behaviour. I hope to provide similar patches for the other utils if there are no objections. Changelog: 2001-02-23 Joshua Daniel Franklin <[EMAIL PROTECTED]> * cygcheck.cc (main): added a --version option * cygch

Re: version information for cygcheck

>The usual thing to do for versions is to get the CVS version number and >apply that. I'm assuming that lines like this in CVS/Entries give the version numbers: /cygcheck.cc/1.22/Tue Jan 29 03:08:42 2002/-ko/ /cygpath.cc/1.13/Thu Jan 17 16:54:01 2002/-ko/ /dump_setup.cc/1.4/Tue Jan 29 18:37:00 2

help/version patches

I've got patches for each of the utils to add/correct the help and version output options. There are 13 in all. I incremented the version number 0.01 from the ones in CVS/Entries with the exception of cygpath. I also added a line based on one found in strace that imbeds the compile date into the v

RE: help/version patches

--- Robert Collins <[EMAIL PROTECTED]> wrote: > Some confusion here: I was meaning that having something like: > const char *revision="$Revision: $ "; > in the file allows you to then use: > const char *version = revision[11]; > to obtain the correct version number. > > Rob I'm not sure I unders

Re: help/version patches

> Adding version numbers is not a bad idea (although, I can't honestly > think of a time when it would have helped to have this information). > Adding version numbers in the middle of the program, in the middle of a > text string is, IMO, a bad idea. The version number should be at > the top of t

Re: help/version patches

> Adding version numbers is not a bad idea (although, I can't honestly > think of a time when it would have helped to have this information). > Adding version numbers in the middle of the program, in the middle of a > text string is, IMO, a bad idea. The version number should be at > the top of t

Re: help/version patches

> Adding version numbers is not a bad idea (although, I can't honestly > think of a time when it would have helped to have this information). > Adding version numbers in the middle of the program, in the middle of a > text string is, IMO, a bad idea. The version number should be at > the top of t

Re: help/version patches

> Adding version numbers is not a bad idea (although, I can't honestly > think of a time when it would have helped to have this information). > Adding version numbers in the middle of the program, in the middle of a > text string is, IMO, a bad idea. The version number should be at > the top of t

Re: help/version patches

> > I'm not sure I understand. Hard-code the revision in a const char > > man co might enlighten you. > I'm afraid I've never used CVS/RCS before. :( Am I reading this right? If I just put $Revision$ in the code, once it's checked in/out that'll be replaced with the correct version number? I s

RE: help/version patches

--- Robert Collins <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Joshua Daniel Franklin [mailto:[EMAIL PROTECTED]] > > +const char *revision="$Revision: 1.22 $"; > > This is suspect: The revision string can look like $R

Re: version information for cygcheck

--- Warren Young <[EMAIL PROTECTED]> wrote: > Joshua Daniel Franklin wrote: > > > > -z, --version output version information and exit > > > > I used -z since -v is --verbose. It could also have no character > > option if that would be better. >

Re: version information for cygcheck

--- Warren Young <[EMAIL PROTECTED]> wrote: > Joshua Daniel Franklin wrote: > > > > -z, --version output version information and exit > > > > I used -z since -v is --verbose. It could also have no character > > option if that would be better. >

Re: version information for cygcheck

--- Warren Young <[EMAIL PROTECTED]> wrote: > Joshua Daniel Franklin wrote: > > > > -z, --version output version information and exit > > > > I used -z since -v is --verbose. It could also have no character > > option if that would be better. >

Re: help/version patches

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > There's no need for a loop. There really shouldn't be any need to > accommodate the missing colon but it doesn't hurt too much to add a test > case. > > I've checked in a modified version of your patch. I cleaned up some of > the non-GNU form

cygpath copyright/version patch

the variable 'o' to prevent a compiler warning. Changelog: 2002-02-27 Joshua Daniel Franklin <[EMAIL PROTECTED]> * cygpath.cc (print_version): New function. (main): Accommodate new version function. Initialize 'o' to prevent warning. ___

Re: cygpath copyright/version patch

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Wed, Feb 27, 2002 at 12:56:34PM -0800, Joshua Daniel Franklin wrote: > >Changelog: > > > >2002-02-27 Joshua Daniel Franklin <[EMAIL PROTECTED]> > > > >* cygpath.cc (print_version): New function

dumper.exe help/version patch

works with all compilers. 2002-03-09 Joshua Daniel Franklin <[EMAIL PROTECTED]> * dumper.cc (usage) Standardize usage output. Generalize to allow use for help. (longopts) New struct. Added longopts for all options. (print_version) New function. (main) Change

getfacl.c help/version patch

2002-03-09 Joshua Daniel Franklin <[EMAIL PROTECTED]> * getfacl.c (usage) Standardize usage output. Change return type to static void. Add exit point within function. (longopts) Added longopts for all options. (print_version) New function.

Re: getfacl.c help/version patch

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > Can I ask you to also take a look at the utils.sgml file and update the > documentation there, too? It should be self-explanatory. > > If you feel like regularizing the presentation in this file so that all > of the options are displayed in the

big kill patch (adds list/help/version)

o. Is there something like strsignal for this, or would it have to be hard-coded? 2002-03-10 Joshua Daniel Franklin <[EMAIL PROTECTED]> * kill.cc (sig0) New function. Process signals given on command line. (usage) Generalize to allow use for help. Describe options. (l

Re: big kill patch (adds list/help/version)

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > No lectures, please. If you want to get rid of a goto, fine. 'twas a joke. Sorry. > I'm sorry but 'kill -l' has an established way of working. > How does the linux kill program handle this? RedHat's prints a list like 1) SIGHUP 2) SI

Re: big kill patch (adds list/help/version)

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > >> How does the linux kill program handle this? > >RedHat's prints a list like > > 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL > > 5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE > >... > >Looks hard-coded to me, but I di

(small) kill.cc patch

Here is a patch that moves the functions in kill.cc to the top. That's all it does. This is for consistency with the other utils. 2001-03-11 Joshua Daniel Franklin <[EMAIL PROTECTED]> * kill.cc (usage) move to top of file (getsig) ditto (force

long-option patch for kill.cc

(not getopt), so I didn't really find what I was looking for. This patch changes the option-handling in kill to use a switch instead of if/else if/else clauses. It also enables basic long-option handling. 2001-03-11 Joshua Daniel Franklin <[EMAIL PROTECTED]> * kill.cc (main): Handle o

long-option patch for kill.cc

Um. And here's the patch. __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ --- kill.cc-origMon Mar 11 19:48:34 2002 +++ kill.cc Mon Mar 11 19:55:19 2002 @@ -1,6 +1,6 @@ /* kill.cc -

mkgroup usage/version patch

03-13 Joshua Daniel Franklin <[EMAIL PROTECTED]> * mkgroup.c (usage): Simplify usage output. Generalize to allow use for help. Correct '?' typo to 'h'. (longopts): Add version option. (opts): Add 'v' version option. (pr

Re: mkgroup usage/version patch

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > While I'm going with the decision to add a version information > I don't understand why you changed > > - the usage output method. I don't like to have a big multiline format > string in fprintf. Well, I could just as easily changed all the li

new mkgroup patch

Here is a new patch that retains the multiple fprintf's instead of using a multiline one in the usage function. Also adds version option, etc.: 2002-03-16 Joshua Daniel Franklin <[EMAIL PROTECTED]> * mkgroup.c (usage): Simplify usage output. Generalize to allow use

mkpasswd patch

/msg00339.html I forgot the attachment the first time and never heard anything more... Thanks. Changelog: 2001-03-19 Joshua Daniel Franklin <[EMAIL PROTECTED]> * mkpasswd.c (usage): Simplify usage output. Generalize to allow use for help. Correct '?' typo to '

stackdump.sgml new file

I was thinking about writing some updated documentation as requested lately on the mailing list (http://www.cygwin.com/ml/cygwin/2002-03/msg01633.html) I've started by writing a new file to document the existance of the cygwin_stackdump() function. ChangeLog: 2001-04-03 Joshua Daniel Fra

Re: stackdump.sgml new file

> 2) The patch is included is an html attachment. > > Obviously 1) is a no-op but we really need just a straight patch in > regular text. > Well, I'm not sure this is what you mean, here is the straight text of the file. Seems kinda silly for one this short. I put it in stackdump.sgml in /src/wi

Patch for mkpasswd

Here is a patch for mkpasswd. It brings mkpasswd up to date with the changes already made to mkgroup. Changelog: 2001-03-19 Joshua Daniel Franklin [EMAIL PROTECTED] * mkpasswd.c (usage): Simplify usage output. Generalize to allow use for help. Correct '?' typo to 'h&

Re: Patch for mkpasswd

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Sat, Apr 27, 2002 at 12:10:03PM -0500, Joshua Daniel Franklin wrote: > Applied. Additionally I've changed all exit() calls in main() to return > statements. Thanks, I will use this from now on. > However, did yo

Re: long-option kill patch

Is there something wrong with the patch for kill.cc? It's a very simple patch: http://www.cygwin.com/ml/cygwin-patches/2002-q2/msg00146.html I'd be happy to fix it if there is something wrong, but I'm not psycic about what... __ Do You Yahoo!? LAU

Re: long-option kill patch

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Sun, May 12, 2002 at 08:30:09PM -0700, Joshua Daniel Franklin wrote: > >Is there something wrong with the patch for kill.cc? > >It's a very simple patch: > > > >http://www.cygwin.com/ml/cygwin-patch

kill.cc version patch

Here is a version option patch against Chris' new kill.cc with signal listing. It also adds a prog_name variable as a small way of helping prevent /bin/kill vs bash's kill confusion. ChangeLog: 2002-05-13 Joshua Daniel Franklin <[EMAIL PROTECTED]> * kill.cc (prog_

getfacl help/version patch

Here is a patch to getfacl that adds longopts for all options, standardizes the usage output, and adds the GNU standard --version option. 2002-05-07 Joshua Daniel Franklin <[EMAIL PROTECTED]> * getfacl.c (usage) Standardize usage output. Change return type to static void.

Re: getfacl help/version patch

> On Mon, May 20, 2002 at 05:33:01PM -0500, Joshua Daniel Franklin wrote: > > Here is a patch to getfacl that adds longopts for all options, > > standardizes the usage output, and adds the GNU standard --version option. > > I'm all for it but the patch doesn't ap

Re: getfacl help/version patch

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Tue, May 21, 2002 at 05:23:22PM -0500, Joshua Daniel Franklin wrote: > > > On Mon, May 20, 2002 at 05:33:01PM -0500, Joshua Daniel Franklin wrote: > > > > Here is a patch to getfacl that adds longopts for all opt

mount --version pathc

Here is a --version patch for mount. I also alphabetized longopts, opts, and the getopt case statement. ChangeLog: 2002-05-22 Joshua Daniel Franklin <[EMAIL PROTECTED]> * mount.cc (version) New global variable. (usage) Standardize usage output. Accomodate new version

setfacl version patch

logical order, with the description of Acl_entries first and then the options in alphabetical order. You might want to take a look and make sure I didn't screw anything up in the description. 2002-05-23 Joshua Daniel Franklin <[EMAIL PROTECTED]> * setfacl.c (usage) Standardize usage

Re: setfacl version patch

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > However, I had to correct your above ChangeLog again, as I had already > with the getfacl patch. You forgot the empty line between the header > and the body and there are colons missing after the name of the functions. > I'm very sorry about thi

ps help, version patch

Here is the --help, --version patch for ps. With, I hope, a proper ChangeLog. 2002-05-13 Joshua Daniel Franklin <[EMAIL PROTECTED]> * ps.cc (prog_name): New global variable. (longopts): Ditto. (opts): Ditto. (usage): New function. (print_version

Re: ps help, version patch

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > Good formatting, wrong date == extremely minor problem. > > Applied. > > Thanks. > > cgf After getting some sleep, I also noticed this line in my usage function: With options, %s outputs the long format by default\n", prog_name, prog_name);

passwd help/version patch

t NUM of days before inactive accounts are disabled (inactive accounts are those with expired passwords) -n, --minageset system minimum password age to MINDAYS -x, --maxageset system maximum password age to MAXDAYS -L, --lengthset system minimum password length to LEN 2002-

Re: passwd help/version patch

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Tue, May 28, 2002 at 10:56:21PM -0500, Joshua Daniel Franklin wrote: > > Here is the --help, --version patch for passwd. > > I used the idea from a recent cygpath patch to separate usage output into > > sections, tho

Re: passwd help/version patch

for LookupAccountSid() with the sec* stuff in winsup/cygwin as a guide, but it looks like reinventing a C wheel from C++ spare parts. It'd be a lot better to be able to just put cygwin_extract_nt_dom_user(pw, domain, (char *) user) right in passwd.c IMHO. Caveat: I don't have a real domain

regtool help/version patch

] == NULL) after the getopt, which was causing a core dump on 'regtool get' with no KEY. ChangeLog: 2002-06-02 Joshua Daniel Franklin <[EMAIL PROTECTED]> * regtool.cc (prog_name): New global variable. (longopts): Ditto. (opts): Ditto. (usage): Standard

Re: regtool help/version patch

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Sun, Jun 02, 2002 at 10:58:33PM -0400, Christopher Faylor wrote: > >On Sun, Jun 02, 2002 at 09:45:30PM -0500, Joshua Daniel Franklin wrote: > >>2002-06-02 Joshua Daniel Franklin <[EMAIL PROTECTED]> > >>

umount version patch

Here is the help/version patch for umount. ChangeLog: 2002-06-03 Joshua Daniel Franklin <[EMAIL PROTECTED]> * umount.cc (version): New global variable. (longopts): Accomodate new --version option. (opts): Ditto. (usage): Standardize usage

ssp.c patch

version part is only a few lines. I could leave the --version part out but this made more sense to me. P.S. I also found two variable-name typos in the run_program (char * cmdline) function and fixed it. ChangeLog: 2002-06-03 Joshua Daniel Franklin <[EMAIL PROTECTED]> * ssp.c

strace patch

Here is a patch for strace that changes the method of version output to be consistent with the other utils. CVS should now automatically update version information. I also changed usage () so that the MASK information will only display with --help. ChangeLog: 2002-06-05 Joshua Daniel Franklin

Re: Patch for sub-second resolution in stat(2)

You know, I had some trouble with this, too. Maybe it would be worth adding to contrib.html that attaching a "ChangeLog.txt" file works well to preserve formatting? --- Conrad Scott <[EMAIL PROTECTED]> wrote: > "Earnie Boyd" <[EMAIL PROTECTED]> wrote: > > Attach the ChangeLog entry to the mail,

passwd edited /etc/passwd patch

2002-06-11 Joshua Daniel Franklin <[EMAIL PROTECTED]> * passwd.c (GetPW): Handle case of user-edited /etc/passwd with cygwin_internal (CW_EXTRACT_DOMAIN_AND_USER, ...) --- passwd.c-orig Tue Jun 11 20:13:51 2002 +++ passwd.cTue Jun 11 19:59:17 2002 @@ -16,6 +16,7

Re: passwd edited /etc/passwd patch

--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Tue, Jun 11, 2002 at 08:18:15PM -0500, Joshua Daniel Franklin wrote: > > + /* Try getting a Win32 username in case the user edited /etc/passwd */ > > + if (ret == NERR_UserNotFound) > > + { > &

cygpath costmetics

now, though, so that code is untested. ChangeLog: 2002-06-18 Joshua Daniel Franklin <[EMAIL PROTECTED]> * cygpath.cc (usage): Clean up usage output. (dowin): Correct output of -t mixed for -ADHPSW options. --- cygpath.cc-orig Tue Jun 18 19:33:22 2002 +++ cygpath

YACP

habetizing of the longopts and options, and various cleanup in usage(). ChangeLog: 2002-06-18 Joshua Daniel Franklin <[EMAIL PROTECTED]> * cygpath.cc (usage): Clean up usage output (more). (main): Change --type option to --mixed; remove '/* nothing */'. Mak

Re: YACP

dos to me should mean short-name as well. So should I put together another patch to do this as well? And BTW, is the UNIXy default OK? --- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Thu, Jun 20, 2002 at 06:17:21PM -0500, Joshua Daniel Franklin wrote: > >YACP (Yet Another Cygpat

Re: YACP

rs now they will get UNIXy path output. I also corrected an apparent bug in the long_options that prevented "close", "file" and "type" from working, even though -c, -f, and -t did. I'm not intimate with getopt but it looks like the flag part of long_options stru

a utils.sgml patch

Joshua Daniel Franklin <[EMAIL PROTECTED]> * utils.sgml: Update screen sections to reflect --help output changes. --- utils.sgml-orig 2002-06-24 18:40:48.0 -0500 +++ utils.sgml 2002-06-24 18:49:21.0 -0500 @@ -8,14 +8,15 @@ specifically for Cygwin. cy

User's Guide DLL building patch

import lib. ChangeLog (this is in the doc subdir): 2002-10-16 Joshua Daniel Franklin <[EMAIL PROTECTED]> * dll.sgml: Clarify discussion of building dlls. --- dll.sgml-orig 2002-10-15 22:48:29.0 -0500 +++ dll.sgml2002-10-15 23:31:47.0 -0500 @@ -39,19 +39,18 @@

grammar in doc/ntsec.sgml

I applied this patch to fix the grammar issues mentioned here: http://www.cygwin.com/ml/cygwin/2002-10/msg01293.html I also applied the earlier patch to doc/dll.sgml mentioned: http://www.cygwin.com/ml/cygwin-patches/2002-q4/msg7.html ChangeLog: 2002-10-22 Joshua Daniel Franklin <[EM

doc patch for CYGWIN codepage=, regtool

3/msg00238.html but it would be great to get patches for utils.sgml whenever a util is patched, or at least a heads-up. 2003-02-02 Joshua Daniel Franklin <[EMAIL PROTECTED]> * cygwinenv.sgml: Add section for "CYGWIN codepage:[ansi|oem]" * dll.sgml: Add

Re: doc patch for CYGWIN codepage=, regtool

> Incidentally, does anyone know where the source of the regtool manpage is? > It should be patched accordingly, but I couldn't find it. (Also replied to in [EMAIL PROTECTED]) >From /usr/doc/Cygwin/cygwin-doc-1.3-2.README : - The two intro pages (intro.1 and intro.3) were written by ha

heap_chunk_in_mb patch

I committed this patch to document heap_chunk_in_mb. 2003-02-05 Joshua Daniel Franklin <[EMAIL PROTECTED]> * setup-net.sgml: Add "setup-maxmem" section * setup2.sgml: New section "setup-maxmem" to document heap_chunk_in_

Re: Produce beeps using soundcard

>From 'man bash': escape sequences, if present, are decoded as follows: \a alert (bell) Wouldn't this be better called "bell" or "alert"? --- Vaclav Haisman <[EMAIL PROTECTED]> wrote: > > Hi, > this small patch adds an ability to produce beeps (\a) using soundcard by > M

Re: mkpasswd & mkgroup

--- "Pierre A. Humblet" <[EMAIL PROTECTED]> wrote: > Earlier I have added a -c switch to mkpasswd & mkgroup. Any progress on documenting these in utils.sgml? __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.co

Re: utils.sgml (was Re: mkpasswd & mkgroup)

> At 02:45 PM 2/25/2003 -0800, Joshua Daniel Franklin wrote: > >Any progress on documenting these in utils.sgml? On Sat, Mar 01, 2003 at 11:43:20AM -0500, Pierre A. Humblet wrote: > Yes! Thanks Pierre! I checked this in with only a small grammatical change. ? utils.sgml-orig ? util

Re: [PATCH] docs/install.texinfo

On Mon, Mar 03, 2003 at 07:29:41PM -0500, Pierre A. Humblet wrote: > here is an upgrade to the FAQ. Actually, the FAQ is davidsb's territory, though it looks good to me.

Patched doc/setup-net.sgml

I just committed a big pactch to doc/setup-net.sgml that more or less documents setup.exe. Resulting HTML can temporarily be seen at: <http://iocc.com/~joshua/cygwin/setup-net.html> 2003-03-22 Joshua Daniel Franklin <[EMAIL PROTECTED]> * setup-net.sgml: Document setup.exe

Re: Patched doc/setup-net.sgml

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Sat, Mar 22, 2003 at 02:11:32PM -0600, Joshua Daniel Franklin wrote: > >I just committed a big pactch to doc/setup-net.sgml that more or less > >documents setup.exe. Resulting HTML can temporarily be seen at: > >

Re: Patched doc/setup-net.sgml

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > >> Feel free to update the cygwin web pages if you want. > > > >OK... how? > > CVS - :ext:cygwin.com:/cvs/cygwin I've got this ready to go, but there are quite a few small differences between the ones in htdocs/cygwin-ug-net and my cygwin-ug-ne

Re: Patched doc/setup-net.sgml

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Sat, Mar 22, 2003 at 12:47:08PM -0800, Joshua Daniel Franklin wrote: > >Is this going to matter? > > No. Committed. __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' N

Improve setup-net.sgml based on comments

I checked in some changes. 2003-03-23 Joshua Daniel Franklin <[EMAIL PROTECTED]> * setup-net.sgml: Improve setup.exe documentation Index: setup-net.sgml === RCS file: /cvs/src/src/winsup/doc/setup-net.sgml,v retr

Re: mkpasswd and mkgroup

--- "Pierre A. Humblet" <[EMAIL PROTECTED]> wrote: > Corinna, Hmm. I feel like I'm eavesdropping. > Following remarks made on the list this patch > - allows to specify several domains at once with -d I just don't understand this one. Can someone be logged into multiple domains at once? > - onl

New Doc section, "Using Cygwin Effectively with Windows"

2003-07-31 Joshua Daniel Franklin <[EMAIL PROTECTED]> * effectively.sgml: New file, "Using Cygwin Effectively with Windows". * legal.sgml: Update year in copyright notice. * using.sgml: Include "Using Cygwin Effectively with Windows" section.

Many updates to winsup/doc

I just committed several changes to winsup/doc. Most are small edits to various sections of the User's Guide, but there are two that I should draw attention to. First, I updated the DTD declaration in the sgml.in files to the official DocBook 4.2 SGML DTD, added a new DSSSL stylesheet called cyg

Are cygwin-ug and cygwin-api-int used?

I would like to remove two build targets from winsup/doc/Makefile.in: cygwin-ug/cygwin-ug.html cygwin-api-int/cygwin-api-int.html As far as I can tell, these are not used for anything and have references to "the GNUPro release". This would not effect the "net release" versions o

Added Quick Start to Users' Guide

I just checked in a couple patches to the Users' Guide. The big news is two short "Quick Start" sections focused on those with Windows or Unix experience. 2004-01-15 Joshua Daniel Franklin <[EMAIL PROTECTED]> * setup-net.sgml: Add "internet-setup" id

Re: Are cygwin-ug and cygwin-api-int used?

On Sun, Jan 11, 2004 at 02:45:20PM -0800, Joshua Daniel Franklin wrote: > I would like to remove two build targets from winsup/doc/Makefile.in: > > cygwin-ug/cygwin-ug.html > cygwin-api-int/cygwin-api-int.html > > As far as I can tell, these are not used for

Re: [UG Patch] kmem and check_case typo

On Fri, 21 May 2004 10:22:20 -0500, Brian Ford <[EMAIL PROTECTED]> wrote: > > On Thu, 20 May 2004, Corinna Vinschen wrote: > > > On May 20 09:22, Igor Pechtchanski wrote: > > > BTW, should /dev/kmem work also? > > > > No, only /dev/mem and /dev/port are working. /dev/kmem is still looking > > fo

Re: ssp.c (usage): Add missing linefeed.

I went ahead and applied this. It doesn't appear to break anything. :) On Mon, 24 May 2004 05:11:51 +0100, John Paul Wallington <[EMAIL PROTECTED]> wrote: > > 2004-05-24 John Paul Wallington <[EMAIL PROTECTED]> > > * ssp.c (usage): Add missing linefeed. > > --- ssp.c 14 Feb 2004

Re: [UG Patch] kmem and check_case typo

> >On Fri, 21 May 2004 10:22:20 -0500, Brian Ford wrote: > >> Ok, then shouldn't we apply the following patch to the users > >> guide? (plus a typo fix) Applied with the "planned for development" euphamism.

keep Cygwin docs well-formed and valid

I just did a commit that touched a lot of sgml files. Now both the User's Guide (cygwin-ug-net.sgml) and API Reference (cygwin-api.sgml) are well-formed and valid DocBook XML. The current SGML tools still work fine with it, but I hope to move the doc Makefile to xmlto soon to end the confusion with

Re: [Patch] Loading cygwin1.dll from MinGW and MSVC

On 6/3/05, Max Kaehn wrote: > This patch contains the changes to make it possible to dynamically load > cygwin1.dll from MinGW and MSVC applications. The changes to dcrt0.cc are > minimal and only affect cygwin_dll_init(). I've also added a MinGW test > program to testsuite and a FAQ so people wi

Re: [Patch] Loading cygwin1.dll from MinGW and MSVC

On 6/4/05, Christopher Faylor wrote: > If you want to me to revert the patch, please let me know. > Otherwise, please just massage it as you see fit. No, not a problem. I'll just edit it a bit.

Re: [Patch]: Changes to how-programming.texinfo

On 7/15/05, Brian Dessent wrote: > Christopher Faylor wrote: > > > Btw, the "other license" provision in the cygwin licensing web page was > > really meant as a way to accommodate other, already existing projects. So do we want to change the wording at all? > Last I checked RHEL and FC were *st

Re: [PATCH] Proposed clarification of the snapshot installation FAQ

On 1/11/06, Igor Peshansky wrote: > As mentioned in , > here's a patch to the FAQ to clarify the section on installing snapshots. > I didn't know whether the various *.texinfo files are still used, so I > ported the modifications there as well, jus