On Apr 29, 2012, at 6:18 PM, Bjarne D Mathiesen wrote:
> Bradley Giesbrecht wrote:
>>
>> On Apr 29, 2012, at 5:00 PM, Bjarne D Mathiesen wrote:
>>
>>> I've attached diffs to all of the postings where I've found a solution
>>> to a problem.
>>
>> Looking back through your emails I'm unsure which ports some of the patches
>> are for.
>>
>> Are you working in an svn repo?
>> If so, from your ports tree could you produce a patch something like this:
>> $ svn diff www/{mod_*,apache2} > patch-apaceh2.4.2+mods.diff
>
> I'm working by hand in bbeditMy editor of choice. > I've got my own local repo for completely new ports (eg sqwi) or for > those that I've heavily modified (eg apache2) > > for those ports that I've > only modified a little bit > am working on pathches for > I've got a patch repo > > sometimes, when I supply a patch, I only submit part of what I do to my > own install as my own modification aren't according to MacPorts policy, > eg I use apxs to install mod_* automatically in apache2 and I supply a > default conf file for them > > now, as to deciphering which port one of my attached diff files belongs > to, it ought not to be that hard to determine it: ;-) > the heading on the message indicates which mod_* port it is > the 1st & 2nd line in the diff tells which mod_* port it is Thanks for the explanation. I'll take a pass at this chore for now. Regards, Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
