public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Sjors Gielen <mailinglist@dazjorz.com>
Cc: cygwin@cygwin.com
Subject: Re: Hosting the Debian/kCygwin port?
Date: Wed, 21 Jan 2009 13:35:00 -0000	[thread overview]
Message-ID: <20090121130726.GL5034@const.bordeaux.inria.fr> (raw)
In-Reply-To: <49771BD8.602@dazjorz.com>

BTW, AIUI from a cygwin point of view, in principle there shouldn't
be any need to patch debian sources: if cygwin behaves differently
from linux, then it's a bug in cygwin.  One exception is of course the
configure target which contains cygwin instead of linux.  Appart from
that, every fix should ideally be in cygwin.  Now you're of course free
to patch things in the debian package so as to make quick progress, but
on the long term there shouldn't be any patch except in configure
scripts.

Samuel

--
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/

  reply	other threads:[~2009-01-21 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20  0:08 Sjors Gielen
2009-01-20  9:54 ` Samuel Thibault
2009-01-21 11:10 ` Carsten Hey
2009-01-21 11:54   ` Carsten Hey
2009-01-21 12:29   ` Samuel Thibault
     [not found]     ` <20090121101813.GH15594@foghorn.stateful.de>
2009-01-21 12:58       ` Sjors Gielen
2009-01-21 13:07         ` Samuel Thibault
2009-01-21 13:17           ` Sjors Gielen
2009-01-21 13:35             ` Samuel Thibault [this message]
     [not found] ` <20090121125918.GP1009@pear.tzafrir.org.il>
2009-01-21 14:17   ` Sjors Gielen
2009-01-21 21:25     ` Christopher Faylor
2009-02-28  0:08 ` David Given
2009-01-21 21:51 Salokine Terata

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=20090121130726.GL5034@const.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=cygwin@cygwin.com \
    --cc=mailinglist@dazjorz.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).