I
plan on applying this acquired knowledge to other builds in the future.
My concerns were raised by how many of the patches I applied (by hand, so
to speak) failed in one or more places. I am afraid I can't serve up all
the examples (maybe a good thing, would have made this message huge). I
c
s 4.9.0-1,
and since my Linux systems use a different version of locate, I hadn't
tested there (nor did I have time to look at the original 4.9.0
source). I'd been hoping any Cygwin patches wouldn't invalidate it; pity.
b) The patch changes the file 'updatedb' whic
under version control.
c) The description says that there are 10 more or less non-trivial
changes in it. A squashed diff of 500 lines on a file with 342 lines
makes reviewing and discussing of each topic impossible.
Would you mind re-sending as separate Git patches?
Have a nice day,
Ber
should have received a copy of the GNU General Public License
# along with this program. If not, see <https://www.gnu.org/licenses/>.
-# csh original by James Woods; sh conversion by David MacKenzie.
+# csh original by James Woods; sh conversion by David MacKenzie;
+# cleanup and enhanc
“import distutils” to resolve to `setuptools._distutils` and
thus bypass any patches that may have been applied to distutils as found in the
stdlib) with an escape hatch: by setting SETUPTOOLS_USE_DISTUTILS=stdlib. Due
to incompatibilities identified with this ereleases, the behavior of using the
._distutils` and
thus bypass any patches that may have been applied to distutils as found in the
stdlib) with an escape hatch: by setting SETUPTOOLS_USE_DISTUTILS=stdlib. Due
to incompatibilities identified with this ereleases, the behavior of using the
local distutils by default was rolled back
Hello Marco,
On 11/30/19 4:23 AM, Marco Atzeri wrote:
> Am 30.11.2019 um 06:44 schrieb Daniel Santos:
>> Hello all,
>>
>> I'm trying to troubleshoot an issue with an old version of rsync on
>> Cygwin. Is there a git repo somewhere with historical patches? The
Am 30.11.2019 um 06:44 schrieb Daniel Santos:
Hello all,
I'm trying to troubleshoot an issue with an old version of rsync on
Cygwin. Is there a git repo somewhere with historical patches? The
version in question is 3.0.4. This is on a remote machine that I can't
change, so I&#
Hello all,
I'm trying to troubleshoot an issue with an old version of rsync on
Cygwin. Is there a git repo somewhere with historical patches? The
version in question is 3.0.4. This is on a remote machine that I can't
change, so I'm trying to decipher what I can from the logs.
Thank you.
There is no documentation for this from 'cygport --help' or 'man
cygport'. Is this an oversight?
Matt D.
On 11/4/2017 9:04 AM, Jon Turney wrote:
On 04/11/2017 10:45, Matt D. wrote:
I've gotten this far:
download cygport
download package src
cd /usr/src/package*
cyg
On 04/11/2017 10:45, Matt D. wrote:
I've gotten this far:
download cygport
download package src
cd /usr/src/package*
cygport package.cygport prep
I can now edit the source, compile, etc. But what is the workflow for
producing a patch file of my changes?
You can use 'cygport diff
I've gotten this far:
download cygport
download package src
cd /usr/src/package*
cygport package.cygport prep
I can now edit the source, compile, etc. But what is the workflow for
producing a patch file of my changes?
Matt D.
--
Problem reports: http://cygwin.com/problems.htm
ygwin. Can the patch in the post against the qt in
the cygwin?
Tatsuro
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/qt-patches-which-seem-to-make-gnuplot-qt-terminal-work-on-cygwin-were-uploaded-on-gnuplot-site-tp118143.html
Sent from the Cygwin list mailing lis
> From: Achim Gratz
> Sent: Thursday, December 18, 2014 6:09 AM
> To: cygwin-a...@cygwin.com
> Subject: Re: cygport patches for TeX Live
>
> Marco Atzeri writes:
> >> /usr/share/postinstall/
> >
> > brain still starting
> >
> > /etc/postinsta
PACKAGE DESCRIPTION
===
Homepage: https://freecode.com/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
t only because I wasn't familiar with out-of-the tree
> >> >> build
> >> >> system. (Had to read building instructions first, yeah...)
> >> >> Now, I'm a happy owner of a custom cygpath that doesn't annoy me with
> >> >
On Sun, Apr 13, 2014 at 02:45:06AM +0400, Andrey Repin wrote:
>Greetings, Corinna Vinschen!
>> As for new functionality and non-trivial patches, I'm sorry but we
>> still need the copyright assignment in this case. I know that people
>> are shying away from it, so I
nloaded whole
>> >> Cygwin /cvs/src, found the offended string, patched the file, and it took
>> >> me 2
>> >> days to rebuild it only because I wasn't familiar with out-of-the tree
>> >> build
>> >> system. (Had to read building instruct
On Sat, Apr 12, 2014 at 04:46:24PM +0200, Corinna Vinschen wrote:
>On Apr 11 13:09, Christopher Faylor wrote:
>> On Fri, Apr 11, 2014 at 02:10:42PM +0200, Corinna Vinschen wrote:
>> >On Apr 11 09:01, Peter Rosin wrote:
>> >>The newlib license is liberal enough for RedHat to relicense it under
>> >>
On Apr 11 13:09, Christopher Faylor wrote:
> On Fri, Apr 11, 2014 at 02:10:42PM +0200, Corinna Vinschen wrote:
> >On Apr 11 09:01, Peter Rosin wrote:
> >>The newlib license is liberal enough for RedHat to relicense it under
> >>their own terms?
> >
> >That's it, more or less.
>
> I have never seen
On Fri, Apr 11, 2014 at 02:10:42PM +0200, Corinna Vinschen wrote:
>On Apr 11 09:01, Peter Rosin wrote:
>>The newlib license is liberal enough for RedHat to relicense it under
>>their own terms?
>
>That's it, more or less.
I have never seen how you can have it both ways, legally speaking. I
was to
employer, after a bit of convincing. I have
> for example helped making Libtool work better on Cygwin (and Windows
> in general). Anything for-profit like Redhat (I did bring it up)
> was just too much, and that discussion ended pretty quickly. Anyway,
> it's not like I'm sitting on
>> system. (Had to read building instructions first, yeah...)
> >> Now, I'm a happy owner of a custom cygpath that doesn't annoy me with
> >> insignificant warnings.
>
> > Wanna send the patch to cygwin-patches(*)?
>
> I'm not quite happy with it yet. I
, found the offended string, patched the file, and it took me
>> 2
>> days to rebuild it only because I wasn't familiar with out-of-the tree build
>> system. (Had to read building instructions first, yeah...)
>> Now, I'm a happy owner of a custom cygpath that doesn
n general). Anything for-profit like Redhat (I did bring it up)
was just too much, and that discussion ended pretty quickly. Anyway,
it's not like I'm sitting on any patches and that lifting that
barrier will open any floodgate from this corner. But that said, I
rarely bother looking at t
that a person who found
the source could provide a patch. That has nothing to do with "web
repos" since the person had already tracked down the code.
>>So, like Andy, pardon me if I'm not moved to tears by your difficulties
>>submitting patches.
>
>My difficulties? I
On Thu, Apr 10, 2014 at 07:39:49PM -0500, Steven Penny wrote:
>On Thu, Apr 10, 2014 at 7:28 PM, Chris J. Breisch wrote:
>>>> So, like Andy, pardon me if I'm not moved to tears by your difficulties
>>>> submitting patches.
>> So, again, pardon me if I
On Fri, Apr 11, 2014 at 01:15:12AM +0200, Peter Rosin wrote:
>On 2014-04-09 19:05, Christopher Faylor wrote:
>> And, this gives me the opportunity to say a belated thank-you to you and
>> other people who have managed, despite all odds, to contribute.
>>
>> Here's a knocked together list from the
On Thu, Apr 10, 2014 at 7:28 PM, Chris J. Breisch wrote:
>>> So, like Andy, pardon me if I'm not moved to tears by your difficulties
>>> submitting patches.
> So, again, pardon me if I'm not moved to tears by your difficulties.
Oops, sorry folks it looks like I
ed to tears by your difficulties
submitting patches.
My difficulties? I dont see your name on this list
http://cygwin.com/ml/cygwin/2014-04/msg00206.html
so perhaps you should get out of that glass house.
I'm not in a glass house, and I'll throw all the rocks I want, thank you
ver
ms such as this. How
do you encourage more people to contribute? well you can start by making it
easier for them, which is what I am proposing.
> So, like Andy, pardon me if I'm not moved to tears by your difficulties
> submitting patches.
My difficulties? I dont see your name on this li
On 2014-04-09 19:05, Christopher Faylor wrote:
> And, this gives me the opportunity to say a belated thank-you to you and
> other people who have managed, despite all odds, to contribute.
>
> Here's a knocked together list from the last 13-or-so years of Cygwin.
*snip*
> Apologies if I missed an
ntage of the time that Christopher can devote towards Cygwin in a
given day is wasted dealing with the issues mentioned above.
Be patient. I've been using Cygwin since...well since before it was
called Cygwin. I think even before it was called Cygwin32. It's come a
long way, and in that
On Wed, Apr 9, 2014 at 8:58 PM, Andrey Repin wrote:
> If all the point you want to make is that YOU don't want to spend time
> supporting the toolset you're using daily, please save your energy.
> My Care-o-meter shows negative readings.
Hey buddy, if you want to spend your days with ad hominem at
cvs/src, found the offended string, patched the file, and it took me 2
> days to rebuild it only because I wasn't familiar with out-of-the tree build
> system. (Had to read building instructions first, yeah...)
> Now, I'm a happy owner of a custom cygpath that doesn't annoy
Greetings, Steven Penny!
> On Wed, Apr 9, 2014 at 11:50 AM, Warren Young wrote:
>> If you think web code repository searching and a public bug tracker are
>> primary barriers to contribution, you aren't being honest with yourself.
>> They are nice, but not necessary.
> I am honest with myself. I,
On Wed, Apr 09, 2014 at 12:43:25PM -0500, Steven Penny wrote:
>On Wed, Apr 9, 2014 at 12:13 PM, Christopher Faylor wrote:
>>It's possible that a site like github has more bandwidth and compute
>>power than sourceware.org and doesn't have to worry about bogging down
>>the system with malicious searc
On Wed, Apr 9, 2014 at 12:13 PM, Christopher Faylor wrote:
> It's possible that a site like github has more bandwidth and compute
> power than sourceware.org and doesn't have to worry about bogging down
> the system with malicious search attacks. We, unfortunately, do. So,
> while it is possible
On Wed, Apr 09, 2014 at 12:02:46PM -0500, Steven Penny wrote:
>On Wed, Apr 9, 2014 at 11:37 AM, Christopher Faylor wrote:
>> I'll once again point out that gdb, binutils, and gcc seem to get by
>> just fine without this. And, maybe I missed something, but I don't see
>> search on sourceforge.net e
On Wed, Apr 9, 2014 at 10:55 AM, Steven Penny <...> wrote:
> 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 incl
On Wed, Apr 09, 2014 at 10:50:20AM -0600, Warren Young wrote:
>I say all of this as one who has expressed a wish for Cygwin to move to
>a better VCS at least once in the past; probably more than once. The
>need to use CVS did not stop me from contributing a few small patches
>ov
On Wed, Apr 9, 2014 at 11:37 AM, Christopher Faylor wrote:
> I'll once again point out that gdb, binutils, and gcc seem to get by
> just fine without this. And, maybe I missed something, but I don't see
> search on sourceforge.net either. Given that, I don't see how this can
> be a huge barrier t
o has expressed a wish for Cygwin to move to
a better VCS at least once in the past; probably more than once. The
need to use CVS did not stop me from contributing a few small patches
over the years. It didn't even present a serious impediment. Further,
I managed to escape the experien
On Wed, Apr 09, 2014 at 12:37:10PM -0400, Christopher Faylor wrote:
>I'll see what I can do about upgrading to using a more modern view which
>allows search. I assume that the contribution floodgate will open.
Actually, I guess I won't. Here's what the web browsing software has to
say about sear
On Wed, Apr 09, 2014 at 09:55:51AM -0500, Steven Penny wrote:
>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 in
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. A
> page and look to the left. You'll see "Contributing" and "Source in CVS".
>> Both lead you to instructions. "Contributing" is intended to help with
>> providing patches. "Source in CVS" is obvious.
>
>I dont think you "get
"Source in CVS".
> Both lead you to instructions. "Contributing" is intended to help with
> providing patches. "Source in CVS" is obvious.
I dont think you "get" my and perhaps other people's workflow. It goes like this
1. discover something that
"Contributing" and "Source in CVS".
Both lead you to instructions. "Contributing" is intended to help with
providing patches. "Source in CVS" is obvious.
Yes, I know. Git is better than CVS.
cgf
--
Problem reports: http://cygwin.com/problems.html
On Tue, Apr 8, 2014 at 1:13 PM, Christopher Faylor wrote:
> It is a little known fact that one of Corinna's early messages was
> actually a suggestion. I suggested to *her* that a patch would be
> considered. She took that as a challenge and provided a patch.
> Apparently Corinna is quite unique
On Tue, Apr 08, 2014 at 05:59:53PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C]
wrote:
>> The whole POINT of this thread was that we want patches.
>
>You've just killed that point, alright. The change I was about, was
>merely a word-long (another keyword to be added),
eb 12, 2014 at 5:58 PM, Andrey Repin wrote:
> Greetings, Michael Verrilli!
>
>> I have been wanting to write some python using the newt (snack)
>> module, so I managed to get it to compile pretty cleanly with some
>> minor patching. Is it appropriate for me to submit pat
Greetings, Michael Verrilli!
> I have been wanting to write some python using the newt (snack)
> module, so I managed to get it to compile pretty cleanly with some
> minor patching. Is it appropriate for me to submit patches here for
> whoever else might have a need? Or should I tr
I have been wanting to write some python using the newt (snack)
module, so I managed to get it to compile pretty cleanly with some
minor patching. Is it appropriate for me to submit patches here for
whoever else might have a need? Or should I try to contact the
maintainer?
This is the tarball I
On 5/2/2013 11:10 AM, Richard Yao wrote:
Where can I find the patches that were applied to python when building
Cygwin's python package?
They would be part of the source package. Fire up 'setup.exe', find the
perl package, and tick the "Src?" column to download the s
Where can I find the patches that were applied to python when building
Cygwin's python package?
signature.asc
Description: OpenPGP digital signature
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
> On Mon, Dec 12, 2011 at 04:57:10PM -0500, Ken Brown wrote:
> >The attached patches address some of the documentation problems mentioned in
> >
> > http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
> >
> >I think the other problems have already been fixed in C
On Mon, Dec 12, 2011 at 04:57:10PM -0500, Ken Brown wrote:
>The attached patches address some of the documentation problems mentioned in
>
> http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
>
>I think the other problems have already been fixed in CVS.
Patch applied along w
The attached patches address some of the documentation problems mentioned in
http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
I think the other problems have already been fixed in CVS.
Ken
--- faq-using.xml.orig 2011-12-08 16:42:26.0 -0500
+++ faq-using.xml 2011-12-12 16:40
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/quilt
License : GPL
Tool to work with series of patches
Program manages a series of patches by keeping track of the changes each
of them makes. They are logically organized as a stack, and you can
apply, un-apply
ikes to keep cygwin 1.5
> supported in gnulib, and probably will do until at least 3 years after
> cygwin 1.7 was first released, since it is still relatively easy to
> install cygwin 1.5 alongside a modern cygwin and test patches against
> both versions. But Bruno also tends to b
ment?
Answering with my gnulib maintainer hat on (and yes, I am one of the
core gnulib maintainers) - Bruno Haible likes to keep cygwin 1.5
supported in gnulib, and probably will do until at least 3 years after
cygwin 1.7 was first released, since it is still relatively easy to
install cygwin 1.5 alo
On 1/27/2011 12:08 PM, Corinna Vinschen wrote:
> Cygwin Versions prior to 1.7.7 are not support anyway.
This is merely semantics. You're saying that *the cygwin project* does
not support older cygwins. However, that doesn't mean *other projects*
have the same policy -- see, for instance, upstream
On Wed, 2010-10-13 at 15:47 +0200, Damien Doligez wrote:
> I think it's a bad idea to have something named "ocaml" that doesn't
> implement the full upstream package. What I will do instead is:
>
> ocaml-base for the system except camlp4
> ocaml-camlp4 for camlp4
> ocamlan empty helper
Yaakov,
> Thanks for updating OCaml to use FlexDLL. There are some further
> patches required for a fully-functional OCaml:
I agree with your suggestions, and I'll use your patches and cygport
file, except for the way you implement this:
> 2) package camlp4 separately due to its
Damien,
Thanks for updating OCaml to use FlexDLL. There are some further
patches required for a fully-functional OCaml:
1) libcamlrun_shared is not a dynlink module, it is a
dynamically-linkable OCaml interpreter (similar to libperl or libpython)
to be used by mod_ocaml. Therefore, it must be
PACKAGE DESCRIPTION
===
Homepage: http://neil.brown.name/blog
License : GPL
A program for applying patches that patch(1) cannot apply due to
conflicting changes in the original. Wiggle will always apply all
changes in the patch to the original. If it cannot find a way to
cleanly
On Apr 11 14:52, Shaddy Baddah wrote:
> Hi,
>
> As some may recall from a previous thread of mine, i turned on
> case-sensitivity in Windows + cygwin, as per:
>
> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
> [...]
> 2. I also found that the ssh-host-config scr
Hi,
As some may recall from a previous thread of mine, i turned on
case-sensitivity in Windows + cygwin, as per:
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
I encountered two issues, for which i have provided the attached patches:
1. I found that there
\>
> Thanks, it seems to be installing now. I think I tried to run cygport
> script
> but it didn't seem to do anything and it wasn't immediately obvious
> what to do. In any case, applying patches one by one as each build
> died seems to have gotten it past that, not s
ason to feed the
> spammers.
> Thanks.
>
>>> On 3/31/2010 7:48 PM, mike marchywka wrote:
>>>> I went ahead and applied the patches and configure at least
>>>> seems to run. I just assumed the patch files were for reference,
>>>> shouldn't the source
te:
I went ahead and applied the patches and configure at least
seems to run. I just assumed the patch files were for reference,
shouldn't the source be patched when downloaded or is there
a reason for this ( or do I have a larger fundamental problem and
applying these patches just lets co
On 3/31/10, Larry Hall (Cygwin) wrote:
> On 3/31/2010 7:48 PM, mike marchywka wrote:
>> I went ahead and applied the patches and configure at least
>> seems to run. I just assumed the patch files were for reference,
>> shouldn't the source be patched when downloaded o
On 3/31/2010 7:48 PM, mike marchywka wrote:
I went ahead and applied the patches and configure at least
seems to run. I just assumed the patch files were for reference,
shouldn't the source be patched when downloaded or is there
a reason for this ( or do I have a larger fundamental proble
e calls etc.
> But, it looks like the first error is missing qt_windows.h.
> What am I supposed to do to get this to build? IThanks.
I went ahead and applied the patches and configure at least
seems to run. I just assumed the patch files were for reference,
shouldn't the source be patched wh
sorry, I gve up on the other build and downloaded the cygwin source.
But, now I'm getting the same errors I got earlier on the other build,
for example,
it looks like problems with "W" and "A" signatures on windoze calls etc.
But, it looks like the first error is missing qt_windows.h.
What am I sup
Bill,
I have a several patches for cmake which I ship in Ports but should
really be moved into the distro. I have used these to build dozens of
packages, including KDE4.
The current patchset is in Ports SVN:
http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/devel/cmake
On 5/11/2009 3:12 PM, Reini Urban wrote:
Ken Brown schrieb:
There is some overlap between the successfully applied patches and
those in icu-3.8-5.src.patch, but I don't think either set of patches
contains the other. Can someone clarify for me what the actual source
patches should be?
7;m not sure exactly which
patches should be applied:
$ cygport icu-3.8-5.cygport prep
>>> Preparing icu-3.8-5
>>> Unpacking source icu4c-3_8-src.tgz
*** Info: applying patch icu-3.8-setBreakType-public.diff:
patching file common/unicode/rbbi.h
*** Info: applying patch icu-3.8-re
I'm building a program (in cygwin-1.7) that comes with its own version
of the icu library. I'd like to patch the source in the same way that
cygwin's icu package does this. But there seems to be a packaging
problem with the icu-3.8-5 source, so that I'm not sure exactly w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> Yaakov (Cygwin/X) wrote:
>> 1) 2.2-export-all-symbols.patch:
>> 2) 2.2-gcc4-libs.patch:
>
> FYI, both of these patches have now been pushed to libtool git master.
Great, thank you.
Yaakov
---
Yaakov (Cygwin/X) wrote:
> 1) 2.2-export-all-symbols.patch:
> 2) 2.2-gcc4-libs.patch:
FYI, both of these patches have now been pushed to libtool git master.
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problem
ven if you've carefully declspec'ed only specific symbols.
If a package is using the -export-dynamic libtool flag, I doubt it would
be using declspec's. But I could be wrong.
> Works for me. Thanks for these patches. Did you already send them
> upstream?
No, I have n
Yaakov (Cygwin/X) wrote:
> I attached two patches for libtool for your consideration:
>
> 1) 2.2-export-all-symbols.patch:
>
> On Cygwin, the --export-all-symbols linker flag is required;
> --export-dynamic has no effect (see
> http://sourceware.org/bugzilla/show_bug.cg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
I attached two patches for libtool for your consideration:
1) 2.2-export-all-symbols.patch:
On Cygwin, the --export-all-symbols linker flag is required;
- --export-dynamic has no effect (see
http://sourceware.org/bugzilla/show_bug.cgi?id
On Mon, Jul 21, 2008 at 10:59:10AM -0400, Ralph Hempel wrote:
> Starting a new thread from an email from about a month ago...
>
> I've got a series of three patches from Reini as follows:
>
> For reference:
> The current three command-line patches at the tracker are all agai
Starting a new thread from an email from about a month ago...
I've got a series of three patches from Reini as follows:
For reference:
The current three command-line patches at the tracker are all against
current HEAD and should applied in the following order:
[EMAIL PROTECTED] /us
> From: Charles Wilson
> Sent: Saturday, 26 April 2008 2:05 p.m.
>
> SourceForge.net wrote:
> > Patches item #1789093, was opened at 2007-09-06 14:33
> >
> > Comment By: Danny Smith (dannysmith)
> > Date: 2008-04-25 17:42
> >
> > Ping!
>
&
SourceForge.net wrote:
Patches item #1789093, was opened at 2007-09-06 14:33
Comment By: Danny Smith (dannysmith)
Date: 2008-04-25 17:42
Ping!
Danny, you'd do better to ping the main mingw [and cygwin] lists.
Comments on sf bugs go to the originator (me -- and I can't do anything
PACKAGE DESCRIPTION
===
Homepage: http://cgi.cse.unsw.edu.au/~neilb/source/wiggle
License : GPL
A program for applying patches that patch(1) cannot apply due to
conflicting changes in the original. Wiggle will always apply all
changes in the patch to the original. If it cannot
PACKAGE DESCRIPTION
===
Homepage: http://www.holgerschurig.de/patcher.html
License : GPL
Patcher is a patch manager that keeps track of which files you change. It
then can generate patches from your changes, no need for you to handle the
diff tool manually. The patches can be
expected. The END key, or any other key apart from those
listed above, quits the key-scrolling mode.
The attached patches are against rxvt-20050409-7.
Whaddaya think?
cheers
mark
--
Mark Robinson
Consultant
Vignette Professional Services
+61 2 9455 5317
"Neither," said Feynman h
On Wed, Sep 05, 2007 at 04:45:23PM -0400, Samuel Robb wrote:
>On Wed, 2007-09-05 at 16:35 -0400, Arlindo da Silva wrote:
>>The sunrpc-4.0.3 package no longer compiles with the current gcc, or
>>g++ of that matter. I've updated some of the K&R style headers so I
>>can now include rpc/xdr.h from my
On Wed, 2007-09-05 at 16:35 -0400, Arlindo da Silva wrote:
> Hi,
>
> The sunrpc-4.0.3 package no longer compiles with the current gcc, or
> g++ of that matter. I've updated some of the K&R style headers so I
> can now include rpc/xdr.h from my C++ sources. I tried to contact the
> previous maintai
Hi,
The sunrpc-4.0.3 package no longer compiles with the current gcc, or
g++ of that matter. I've updated some of the K&R style headers so I
can now include rpc/xdr.h from my C++ sources. I tried to contact the
previous maintainer (Sam Robb) by the e-mail bounced.
In any case, I have posted a pat
On Jul 13 10:00, Corinna Vinschen wrote:
> I'm still not sure how to handle situations where the default config
> file in /etc/defaults/etc has changed between releases, but the user has
> also changed the copied config file in /etc. We have no mechanism and
> no standarized way to handle this so
1 - 100 of 156 matches
Mail list logo
