From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: We need steenking patches (Re: Cygwin kill utility...)
Date: Wed, 09 Apr 2014 14:55:00 -0000 [thread overview]
Message-ID: <CAAXzdLXxAnB0JYHuvJj44ZAT=Uc-G12Xt+xsirnmiPBkOJ4U-w@mail.gmail.com> (raw)
In-Reply-To: <20140409055117.GA1878@ednor.casa.cgf.cx>
On Wed, Apr 9, 2014 at 12:51 AM, Christopher Faylor wrote:
> Except for the lack of an advertised bugzilla link at the Cygwin web
> page, Cygwin is like every one of the other projects hosted at
> sourceware.org/gcc.gnu.org. This includes thriving projects like gcc,
> binutils, gdb, and others. All of the developers in those projects were
> able to figure out how to find CVS (svn, git) web information and,
> eventually, check out their stuff.
I see now you have Stockholm Syndrome with CVS. Perhaps you missed the question,
so I will repeat it:
Where is the online search function for the mailing list and code base? With
GitHub you can use this
http://github.com/svnpenn/bm/search?q=asdf
and it will search all issues and code for a repository. Cygwin appears to have
no web based way of searching either, besides a Google search. That is sad.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-04-09 14:55 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 3:01 Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ? Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-04-08 3:18 ` Christopher Faylor
2014-04-08 3:30 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-04-08 9:01 ` Corinna Vinschen
2014-04-08 13:19 ` Buchbinder, Barry (NIH/NIAID) [E]
2014-04-08 13:34 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-04-08 15:21 ` Christopher Faylor
2014-04-08 16:27 ` Tim Prince
2014-04-08 16:49 ` Christopher Faylor
2014-04-08 17:46 ` Corinna Vinschen
2014-04-08 18:00 ` Christopher Faylor
2014-04-08 17:59 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-04-08 18:13 ` We need steenking patches (Re: Cygwin kill utility...) Christopher Faylor
2014-04-09 2:21 ` Steven Penny
2014-04-09 3:28 ` Christopher Faylor
2014-04-09 5:04 ` Steven Penny
2014-04-09 5:51 ` Christopher Faylor
2014-04-09 14:55 ` Steven Penny [this message]
2014-04-09 16:37 ` Christopher Faylor
2014-04-09 16:49 ` Christopher Faylor
2014-04-09 16:50 ` Warren Young
2014-04-09 17:02 ` Steven Penny
2014-04-09 17:13 ` Christopher Faylor
2014-04-09 17:43 ` Steven Penny
2014-04-09 19:14 ` Christopher Faylor
2014-04-10 2:05 ` Andrey Repin
2014-04-10 8:01 ` Corinna Vinschen
2014-04-11 11:05 ` Andrey Repin
2014-04-11 12:10 ` Corinna Vinschen
2014-04-12 22:50 ` Andrey Repin
2014-04-12 22:59 ` Christopher Faylor
2014-04-14 8:06 ` Corinna Vinschen
2014-04-10 13:05 ` Steven Penny
2014-04-10 15:12 ` Chris J. Breisch
2014-04-11 0:11 ` Steven Penny
2014-04-11 0:28 ` Chris J. Breisch
2014-04-11 0:39 ` Steven Penny
2014-04-11 2:40 ` Christopher Faylor
2014-04-11 2:46 ` Christopher Faylor
2014-04-09 17:05 ` Christopher Faylor
2014-04-10 23:15 ` Peter Rosin
2014-04-11 2:17 ` Christopher Faylor
2014-04-11 7:01 ` Peter Rosin
2014-04-11 12:10 ` Corinna Vinschen
2014-04-11 17:09 ` Christopher Faylor
2014-04-12 14:46 ` Corinna Vinschen
2014-04-12 16:56 ` Christopher Faylor
2014-04-09 17:09 ` Robert Pendell
2014-04-08 15:44 ` Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ? Adam Dinwoodie
2014-04-08 15:50 ` Corinna Vinschen
2014-04-08 16:24 ` Christopher Faylor
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='CAAXzdLXxAnB0JYHuvJj44ZAT=Uc-G12Xt+xsirnmiPBkOJ4U-w@mail.gmail.com' \
--to=svnpenn@gmail.com \
--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).