Date: Wed, 25 Jul 2012 10:50:12 GMT From: Michael Scheidell <michael.scheidell@secnap.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/170010: [UPDATE] chinese/fcitx and its addons to 4.2.5 Message-ID: <201207251050.q6PAoCxK005382@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/170010; it has been noted by GNATS.
From: Michael Scheidell <michael.scheidell@secnap.com>
To: <bug-followup@FreeBSD.org>, <lichray@gmail.com>
Cc:
Subject: Re: ports/170010: [UPDATE] chinese/fcitx and its addons to 4.2.5
Date: Wed, 25 Jul 2012 06:41:22 -0400
--------------080609050504020403080604
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
almost.
ls
CHANGES MOVED Tools
patch-data_CMakeLists.txt.orig
COPYRIGHT Makefile UIDs security
GIDs Mk UPDATING
KNOBS README chinese
LEGAL Templates patch-data_CMakeLists.txt
seems that (for some reason), it puts the NEW patch file in ../ and does
not follow index.
(i did:
cd /usr/ports
patch -EuN -I -i /tmp/patch.txt, and it (i hope) put all but the new
patch in the right dir (see above)
from now on, you must put EACH PORT in its own attachment, and list the
fact that you are patching four different ports. or, you must open 4
prn's and make sure you let the ocmmitter know to link them together.
If you think this is too much work, consider the committer has to split
your patch apart, guess which patch goes where, and, due to this, a
committer who takes a quick glance at your pr's will most likely skip by
it to get one that is easier to work.
lets try that next time, I don't know if send-pr can attach 4 different
patches, but it seems that Index.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
______________________________________________________________________
--------------080609050504020403080604
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
almost.<br>
<br>
ls<br>
CHANGES MOVED Tools
patch-data_CMakeLists.txt.orig<br>
COPYRIGHT Makefile UIDs
security<br>
GIDs Mk UPDATING<br>
KNOBS README chinese<br>
LEGAL Templates patch-data_CMakeLists.txt<br>
<br>
<br>
seems that (for some reason), it puts the NEW patch file in ../ and
does not follow index.<br>
<br>
(i did:<br>
cd /usr/ports<br>
patch -EuN -I -i /tmp/patch.txt, and it (i hope) put all but the new
patch in the right dir (see above)<br>
<br>
from now on, you must put EACH PORT in its own attachment, and list
the fact that you are patching four different ports. or, you must
open 4 prn's and make sure you let the ocmmitter know to link them
together.<br>
<br>
If you think this is too much work, consider the committer has to
split your patch apart, guess which patch goes where, and, due to
this, a committer who takes a quick glance at your pr's will most
likely skip by it to get one that is easier to work.<br>
<br>
lets try that next time, I don't know if send-pr can attach 4
different patches, but it seems that Index.<br>
<br>
<br>
<div class="moz-signature">-- <br>
Michael Scheidell, CTO<br>
o: 561-999-5000<br>
d: 561-948-2259<br>
<font color="#999999">></font><font color="#cc0000"> <b>| </b></font>SECNAP
Network Security Corporation
<style type="text/css">
<!--
.unnamed1 {
margin: 1em;
padding: 1px;
} -->
</style>
<ul class="unnamed1">
<li>Best Mobile Solutions Product of 2011</li>
<li>Best Intrusion Prevention Product</li>
<li>Hot Company Finalist 2011</li>
<li>Best Email Security Product</li>
<li>Certified SNORT Integrator</li>
</ul>
</div>
<br>
<div id="disclaimer.secnap.com"><hr />This email has been scanned and certified safe by SpammerTrap®.</div>
<div>For Information please see
<a href="http://www.spammertrap.com/">http://www.spammertrap.com/</a>; <hr /></div>
<br>
</body>
</html>
--------------080609050504020403080604--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207251050.q6PAoCxK005382>