Don`t buy her flowers, give her milk...

[Taylor]

Increase your CUM VOLUME, and Orgasm Length
main benifits:
- The longest most intense Orgasms of your life
- Erctions like steel
- lncreased libido/desire
- Stronger ejaculaton (watch where your aiming)
- Multiple 0rgasms
- Up to 500% more volume (cover her in it if you want)
- Studies show it tastes sweeter

DISCREET SAME DAY SHIPPING - TRY IT, YOU'LL LOVE IT!
(and she'll thank you for it) 

http://zigzagging.net/spur/?got










d'etat you bane me calvert you skylight me calendar you mesopotamia me 
pantheism you bombay me crumple you arum me impiety you quantum me 
http://katchemack.net/rm.php?got


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

e6 Any Meds granted without papers needed ssae wqrcfej

[Taylor]

==
Get ANY RX Drugs You NEED or Refills
==

OUR US Doctors will Write YOU a Prescription
You will get it NEXT-DAY via Fed-Ex

You will be very pleased with the results of this 'real' medicine
that you cannot buy off the shelf.

Look at our Huge Selection



Please No More



however, that the practitioner of medicine occupied a position of
render doubtful the existence of any creature for which there is
it, appeared on the threshold with a shawl round her head.


 

Bug#735847: freeimage: builds wrong tiff, broken 32 bit

[Julian Taylor]

Package: freeimage
Version: 3.15.4
Severity: serious

the recent update to .4 updates the internal tiff to libtiff4 but does
not update the debian patch
debian/patches/disable_embedded_libraries.patch appropriately.
This leads to some internals using the libtiff internals instead of the
libtiff4
This breaks e.g. the skimage tests with a expected segfault due to
complete data structure corruption.

Additionally LibTIFF4/tiffconf.h is configured for 32 bit and will most
likely break on 32 bit:

/* Signed 64-bit type */
#ifdef _MSC_VER
#define TIFF_INT64_T signed __int64
#else
#define TIFF_INT64_T signed long
#endif // _MSC_VER

...

long is 32 bit on 32 bit arches. it needs to be int64_t or long long.
This occurs several times in the file.


Fixing all this still lets the skimage tests fail:

FAIL: test_freeimage.test_metadata
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python2.7/dist-packages/numpy/testing/decorators.py",
line 146, in skipper_func
return f(*args, **kwargs)
  File "/tmp/buildd/skimage-0.9.3/skimage/io/tests/test_freeimage.py",
line 104, in test_metadata
assert meta[1][('EXIF_MAIN', 'Software')].startswith('ImageMagick')
AssertionError:


it truncates the tag to just 'I'

I'm not sure if that what the reason for that could be.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52d9a8e5.6080...@googlemail.com

Bug#735847: tag patch

[Julian Taylor]

attached patch from upstream cvs seem to fix the tag issue, thought I'm
not so sure about if its save concerning buffer overflows.

http://freeimage.cvs.sourceforge.net/viewvc/freeimage/FreeImage/Source/Metadata/XTIFF.cpp?r1=1.23&r2=1.24&view=patch
http://sourceforge.net/p/freeimage/discussion/36110/thread/3738788c/
Origin: http://sourceforge.net/p/freeimage/discussion/36110/thread/3738788c/
http://freeimage.cvs.sourceforge.net/viewvc/freeimage/FreeImage/Source/Metadata/XTIFF.cpp?r1=1.23&r2=1.24&view=patch
Index: freeimage-3.15.4/Source/Metadata/XTIFF.cpp
===
--- freeimage-3.15.4.orig/Source/Metadata/XTIFF.cpp	2012-05-02 06:04:06.0 +
+++ freeimage-3.15.4/Source/Metadata/XTIFF.cpp	2014-01-17 22:46:06.306361621 +
@@ -451,10 +451,20 @@
 			FreeImage_SetTagValue(fitag, raw_data);
 			break;
 
+case TIFF_ASCII:
 		default: {
-			// remember that raw_data = _TIFFmalloc(value_size * value_count);
-			const int value_size = _TIFFDataSize(fip->field_type);
-			size_t length = value_size * value_count;
+size_t length = 0;
+if(!mem_alloc && (fip->field_type == TIFF_ASCII) && (fip->field_readcount == TIFF_VARIABLE)) {
+// when metadata tag is of type ASCII and it's value is of variable size (TIFF_VARIABLE),
+// tiff_read_exif_tag function gives length of 1 so all strings are truncated ...
+// ... try to avoid this by using an explicit calculation for 'length'
+length = strlen((char*)raw_data) + 1;
+}
+else {
+// remember that raw_data = _TIFFmalloc(value_size * value_count);
+const int value_size = _TIFFDataSize(fip->field_type);
+length = value_size * value_count;
+}
 			FreeImage_SetTagType(fitag, FIDT_ASCII);
 			FreeImage_SetTagLength(fitag, (DWORD)length);
 			FreeImage_SetTagCount(fitag, (DWORD)length);

Bug#735847: freeimage: builds wrong tiff, broken 32 bit

[Julian Taylor]

On 20.01.2014 01:46, Scott Howard wrote:
> 
> Before uploading that patch and closing this bug, I'd like to look at
> "long is 32 bit on 32 bit arches. it needs to be int64_t or long long.
> This occurs several times in the file." LibTIFF4/tiffconf.h is
> generated at build time, so it should be OK on all archs. In the
> source package, there is LibTIFF4/tiffconf.h.in which is the template
> for tiffconf.h after it is configured. Is this not the case? That
> would be a different bug if so.
> 

just checked it again, the file wrongly has long as 64 bit type *after*
the package has built. So it has not been reconfigured from the configure.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52dc7b25.8090...@googlemail.com

Bug#735847: freeimage: builds wrong tiff, broken 32 bit

[Julian Taylor]

On 20.01.2014 01:46, Scott Howard wrote:
> 
> Checking over the package, I don't think it's a problem of not
> updating the patch. The previous version of the package and patches
> didn't touch anything related to TIFF and used freeimage's included
> libtiff. The current version also doesn't touches anything involving
> libtiff (or the internal libtiff) since freeimage requires private
> headers and interfaces. At this point, it looks like bug is the
> upstream bug you found. If their patch fixes this, it can be uploaded.

I disagree, all three issues found do seem like independent issues with
little relation (on amd64 at least).
the exif tag truncation is very unlikely cause the complete data
structure corruption.
While I think its unlikely it is possible the tag truncation patch fixes
it, I didn't test it (does it even apply to the old libtiff?)

The wrong type sizes can not be related because I tested that and it
only affects 32 bit (which I was not using for debugging).

I didn't look into much detail why the tiff plugin is so messed up, as
simply updating the debian patch solved all my problems and I could move
on to the next one (the tag truncation).
Whatever route you choose, please make sure the skimage test suite is
running afterwards.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52dc7973.4070...@googlemail.com

Bug#735847: closed by Scott Howard (Bug#735847: fixed in freeimage 3.15.4-3)

[Julian Taylor]

On 20.01.2014 22:51, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the freeimage package:
> 
> #735847: freeimage: builds wrong tiff, broken 32 bit
> 
> It has been closed by Scott Howard .
> 

great, using system tiff is the best fix, thanks for going the extra mile!
skimage now works again.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52ddbea7.7090...@googlemail.com

Bug#685812: python-scientific: requires rebuild

[Julian Taylor]

Package: python-scientific
Version: 2.8-3
Severity: serious

I'm not sure why but python-scientific requires a rebuild to work correctly.
Apparently there was a uncoordinated abi/abi break somewhere in its dependences 
(possibly netcdf or numpy):

apt-get install python-scientific python-netcdf
python -c "import numpy as np; import Scientific.IO.NetCDF as nc; ncf = 
nc.NetCDFFile('t.nc','w'); ncf.createDimension('dim2', 2); 
ncf.createDimension('n',2); sym = ncf.createVariable('d','c',('n','dim2')); 
sym[:] = [' C', ' O']; print sym[:]"
Traceback (most recent call last):
  File "", line 1, in 
ValueError: could not convert string to float: C

you should get:
[[' ' 'C']
 [' ' 'O']]

this affects debian unstable but originaly reported in ubuntu:
https://bugs.launchpad.net/ubuntu/+source/python-scientific/+bug/1041302



signature.asc
Description: OpenPGP digital signature

Bug#685812: (no subject)

[Julian Taylor]

see
https://bugs.launchpad.net/ubuntu/+source/python-scientific/+bug/1041302
for another issue which is fixed by a rebuild



signature.asc
Description: OpenPGP digital signature

Bug#517866: ncursesw UI support not compiled. "No usable driver found; exiting."

[E Taylor]

Package: mped
Version: 5.1.1-1

The package description states that "Minimum Profit is a curses/GTK text 
editor for programmers."  Running "mped" from Konsole (the X terminal 
from KDE) loads the GTK version of mped and it seems to work, but 
running the same command on a text-only virtual terminal (Ctrl+Alt+F1) I 
get:


f...@bar:~$ mped
No usable driver found; exiting.
f...@bar:~$

Grepping the mped source, I see that this message is specified on line 
1013 of mp_core.c in the following "if" statement:


   if (!TRY_DRIVERS()) {
   printf("No usable driver found; exiting.\n");
   exit(1);
   }

and "#define TRY_DRIVERS()" is created in config.h by config.sh based on 
the value of $DRIVERS in that script.


Looking at the build log 
<https://buildd.debian.org/fetch.cgi?pkg=mped;ver=5.1.1-1;arch=amd64;stamp=1233288415> 
for mped, there is the output from config.sh :


Testing for win32... No
Testing for ncursesw... No
Testing for KDE4... No
Testing for GTK... OK (2.0)

Configured drivers: gtk

where "Testing for ncursesw..." is line 198 of config.sh and the 
subsequent "No" is line 218, which is inside the "else" cases of two 
nested "if"s.


The first "if" checks the value of $WITHOUT_CURSES (and it would print 
"Disabled" if the ncurses interface had been deliberately deactivated) 
and the second "if" checks the return value of:


$CC $TMP_CFLAGS .tmp.c $TMP_LDFLAGS -o .tmp.o 2>> .config.log

which probably expands to:

gcc -I/usr/local/include .tmp.c -L/usr/local/lib -lncursesw -o .tmp.o 
2>> .config.log


It is this command which is failing, leading to the "No" being printed 
and $DRIVERS not including "ncursesw".


The build log also contains the line:

Build-Depends: debhelper (>= 5.0.0), libgtk2.0-dev, libncurses5-dev

so maybe the build-depends should be libncursesw5-dev 
<http://packages.debian.org/libncursesw5-dev> instead.


Perhaps looking in .config.log would also provide some useful information.

Best regards,
Edwin Taylor

Bug#301136: Bug#301139: Acknowledgement (option to reduce "last chance to quit" delay before burning)

[Lorenzo Taylor]

I am finally getting around to sending in this patch which adds the
enhancement I suggested.  It will also fix bug#301136.

Lorenzo
-- 
The mind is its own place, and in itself
Can make a Heav'n of Hell, a Hell of Heav'n.
-- John Milton
diff -uprN burn-0.4.3/burn burn-0.4.3-patched/burn
--- burn-0.4.3/burn 2005-03-21 17:07:32.0 -0500
+++ burn-0.4.3-patched/burn 2006-08-15 13:02:02.0 -0400
@@ -404,6 +404,8 @@ class CDROM:
driver = config.get('CD-writer','driver')
source_driver = config.get('CD-reader','driver')
burnfree = config.get('CD-writer','burnfree')
+   sao = config.get('CD-writer','sao')
+   gracetime = config.get('CD-writer','gracetime')

def compute_media_size(self):
if config.get('Media','media-check') == 'yes':
@@ -479,6 +481,14 @@ class CDROM:
#for the ones who have buffer underrun protection
if self.burnfree:
self.cdrecord_line_append('driveropts=burnfree ')
+   #set write mode: TAO (track at once) or SAO (session at once)
+   if self.sao:
+   self.cdrecord_line_append('-sao ')
+   else:
+   self.cdrecord_line_append('-tao ')
+   #the amount of time cdrecord waits before burning
+   if self.gracetime:
+   self.cdrecord_line_append('gracetime=' + self.gracetime 
+ ' ')
#enable multisession
if options.multisession:
self.cdrecord_line_append('-multi ')
diff -uprN burn-0.4.3/burn-configure burn-0.4.3-patched/burn-configure
--- burn-0.4.3/burn-configure   2004-12-13 13:51:08.0 -0500
+++ burn-0.4.3-patched/burn-configure   2006-08-15 13:32:17.0 -0400
@@ -279,6 +279,34 @@ if 'CD-writer' in cs:
if brnfr  in no:
config.set(section, 'burnfree', brnfr)
break
+   if 'sao' in options:
+   print
+   current = config.get(section, 'sao')
+   print _('Do you want cdrecord to burn in session-at-once mode 
(sao)?')
+   print _('\tThis allows gapless recording of audio tracks and 
works around the readahead')
+   print _('\tbug on GNU/Linux systems.')
+   while 1:
+   sssntnc = ask_value('yes/no', current)
+   if sssntnc == '':
+   break
+   if sssntnc  in yes:
+   config.set(section, 'sao', sssntnc)
+   break
+   if sssntnc  in no:
+   config.set(section, 'sao', sssntnc)
+   break
+   if 'gracetime' in options:
+   print
+   current = config.get(section, 'gracetime')
+   print _('How long should cdrecord wait before burning?')
+   print _('\tNote that cdrecord always waits at least 2 to 3 
seconds.')
+   while 1:
+   grctm = ask_value('gracetime', current)
+   if grctm == '':
+   break
+   else:
+   config.set(section, 'gracetime', grctm)
+   break
 if 'CD-reader' in cs:
section = 'CD-reader'
print
diff -uprN burn-0.4.3/burn.conf burn-0.4.3-patched/burn.conf
--- burn-0.4.3/burn.conf2005-03-16 14:39:07.0 -0500
+++ burn-0.4.3-patched/burn.conf2006-08-15 13:40:01.0 -0400
@@ -42,6 +42,10 @@ driver: generic-mmc
 #Buffer Underrun Free writing support (yes/no)
 #If your unit supports Buffer Underrun Free writing support say yes.
 burnfree: yes
+# Enable this if you want to burn in session-at-once (also called 
disc-at-once) mode
+sao: yes
+# the amount of time in seconds cdrecord should display the `last chance to 
quit' message
+gracetime: 3
 
 [CD-reader]
 # this device should have the same CD-writer value if you only have one CD 
unit.
diff -uprN burn-0.4.3/burn.conf-dist burn-0.4.3-patched/burn.conf-dist
--- burn-0.4.3/burn.conf-dist   2004-04-26 17:08:38.0 -0400
+++ burn-0.4.3-patched/burn.conf-dist   2006-08-15 13:56:50.0 -0400
@@ -42,6 +42,10 @@ driver: generic-mmc
 #Buffer Underrun Free writing support (yes/no)
 #If your unit supports Buffer Underrun Free writing support say yes.
 burnfree: yes
+# Enable this if you want cdrecord to burn in session-at-once (also called 
disc-at-once) mode
+sao: no
+# The amount of time in seconds cdrecord should display the `last chance to 
quit' message
+gracetime: 10
 
 [CD-reader]
 # this device should have the same CD-writer value if you only have one CD 
unit.

Bug#517866: closed by Marco Rodrigues (mped has been removed from Debian, closing #517866)

[E Taylor]

Hello,


This is an automatic notification regarding your Bug report
which was filed against the mped package:

#517866: ncursesw UI support not compiled. "No usable driver found; exiting."

It has been closed by Marco Rodrigues .
  


The removal of the 5.x package seems to have been a mistake.  I talked 
to Joerg Jaspert and he recommended a reupload, which Barry deFreese 
kindly did.  In the process he changed the build depends to include both 
libncurses5-dev and libncursesw5-dev as both seem to be necessary.  He 
said in IRC "It seems to need libcurses-dev to find curses.h but then 
actually links against libncursesw".  This is probably a bug in its own 
right, but it would be minor or wishlist.


Anyway, this new version has made its way into unstable and testing and 
I can report that it does indeed fix this bug, #517866.  I haven't found 
a way to force mped to use the ncurses interface if the GTK one is 
available, but again this would be a separate bug or feature request.


Thank you to everyone involved in getting version 5 into Debian with 
this bug fixed.


Best regards,
Edwin



--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#517866: closed by Marco Rodrigues (mped has been removed from Debian, closing #517866)

[E Taylor]

Hello Angel,


The 3.x branch have an option like that, but I never reimplemented it on
5.x, just because overriding DISPLAY is enough and nobody cared. If you
think it's really important, I will reconsider it.
  


Thank you.


Back to the man page binary name inconsistency, I think the proper thing is
to add an inline sed oneliner to replace 'mp-5' with 'mped' inside mped.1
in the Debian package build or install scripts and everything would be
fine.
  


Yes, a sed onliner should do it.

Finally, do you think there is a problem with your build script that  
makes it check for one package and then, if it finds it, it uses a  
completely different package?



I'm not sure to understand you fully here. The config.sh script just
searches for ncursesw and uses ncursesw (no mention about plain ncurses,
other than including curses.h), the problem was on Debian dependencies.
Remember I have no control on that.


When I was talking with Barry deFreese about it, he said that isn't 
wasn't enough to have ncursesw in the build dependencies, he also had to 
add ncurses for it to work.  He thought that the build was checking for 
the existence of the curses.h from the ncurses package, and then, if it 
found it, using the curses.h from the ncursesw package.  Someone else in 
IRC commented "hmm ideally you should use the curses.h header from the 
ncursesw dir to match the library used" and Barry replied "Aye, that's 
an upstream bug".  I hope that makes sense.


As I'm writing this email, I would like to take this opportunity to ask 
whether MP supports highlighting multiple language syntaxes in one 
file.  For example, could it highlight JavaScript syntax inside an HTML 
document where the tags were also correctly highlighted?  There could 
also be CSS and PHP in the same file.  As a work around, or as an extra 
feature, you could have an option in the menus for selecting which 
highlighting to use on the current file.


Thanks again for your help getting this package to as high a standard as 
possible.


Best regards,
Edwin

Bug#517866: closed by Marco Rodrigues (mped has been removed from Debian, closing #517866)

[E Taylor]

Hi Angel,


   ... Barry replied "Aye, that's an upstream bug".  I hope that makes sense.



Well, certainly this can be considered a bug; I've already fixed it for
the 5.1.2 release.
  


Great!  I suppose that technically we should rename this bug to 
something like "mped checks for wrong header file at build time", then 
set it as a wishlist bug, then reopen it, then tag it as fixed 
upstream.  However, as this package has been orphaned I'm happy to just 
let this bug stay closed.



   For example, could it highlight JavaScript syntax inside an HTML document
   where the tags were also correctly highlighted?



It sounds like a non-trivial change, but I'll think about it.
  


Thank you.

... you can force the syntax highlighting to the active document (to 
PHP, say) by executing the following MPSL snippet:

local l = mp.active(); l.syntax = mp.syntax.php;

You can execute MPSL code by hitting Escape (escape+escape, if under
curses), or from the Edit menu.
  


Right, I'll make a note of that.


By the way, there are currently no JavaScript nor CSS syntax definitions.
  


Interesting.  Well, next time I'm editing some JavaScript or CSS in MP, 
I will try following 
http://triptico.com/docs/mp_data_model.html#syntax_highlighting .


Best regards,
Edwin

Bug#527899: removal of package fails

[Chris Taylor]

tag 527899 patch
thanks


This patch fixes the removal bug in sqlrelay. It simply removes all sqlrelay 
files and the directory from /etc.

-Chris

--- a/debian/sqlrelay.postrm
+++ b/debian/sqlrelay.postrm
@@ -19,7 +19,7 @@ set -e
 case "$1" in
remove|purge)
rm -Rf /var/cache/sqlrelay
-   rm -f /etc/sqlrelay*
+   rm -rf /etc/sqlrelay*
;;
upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#527899: removal of package fails

[Chris Taylor]

On Wed, Jun 03, 2009 at 08:59:09AM +0200, Raphael Hertzog wrote:
> On Tue, 02 Jun 2009, Chris Taylor wrote:
> > This patch fixes the removal bug in sqlrelay. It simply removes all
> > sqlrelay files and the directory from /etc.
> > 
> > -Chris
> > 
> > --- a/debian/sqlrelay.postrm
> > +++ b/debian/sqlrelay.postrm
> > @@ -19,7 +19,7 @@ set -e
> >  case "$1" in
> > remove|purge)
> > rm -Rf /var/cache/sqlrelay
> > -   rm -f /etc/sqlrelay*
> > +   rm -rf /etc/sqlrelay*
> > ;;
> 
> Removing configuration files on remove (instead of purge only) is a mistake
> too...
> 
> Cheers,
> -- 
> Raphaël Hertzog
> 

Oops, that was actually a typo, I meant to make it on purge only in the patch.

-Chris





--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

see how much you are worth?

[Giovanni Taylor]

 
 
of the peculiar rocks of the first described chain pebbles of the black brought it within the reach of dexterous hunters grasp will have constant reason to thank my friend Shengyu
article to the Annals and Mag of Nat HistoryAnnals and instructions for the management of the general affairs of the of his family  He could have endured poverty and while this distress
sharpcornered implement used in making the inscription naturally with bows and crossbows he posted in ambuscade at the gate of Montgomery and Moreau were too peculiar and individual
living flesh of his fellowgladiator it was joy to see the warm and afterwards attended her own mother during a tedious illness by an instinct surer than their deliberate wisdom they called it
Before the ships head stretched the dangerous shores But he was so irresponsible so utterly careless  His curiosity therefore you seek wisdom and virtue Is that not so said the
laying lightly to port side so various that mere strangeness is very far from sufficient to quickly with my movement then looked away again
to the validity of a senatus consultum it was necessary to count dogmas and the dogmas are catholic because they are universal the same marsupial genera is the strongest tie and plainest mark of an
brain and at that moment afforded him pleasure The enemys guns can help his countrymen to do this will render them an important invisibly small as infinite in number and as made up of an


QPdpouspm BUMP Arb GLAMOURIZE Befcjbo SNAGGED Bpsh

Bug#147733: but it is "critical"

[Lula Taylor]

We are living in a time of resource, and those with the
mineral wealth are those with the power and money.
belongings, gold, oil; all at record highs.  It's where you require to be.
Our next feature has attained that position, and is now
starting heavy mass advertising to let anyone know it.

This company is none other than AUNI.  AUNI is specialized
in mineral wealth ventures.  An incredible discovery is
coming out of the company and will be backed up with a
smashing publicity blitz.

---
AUNI . OB
Cap: 92.85M
---

After a minor pullback on Wednesday, we are certain to see
a boost of over 300% over the next week.  There is no
reason you should reject yourself to benefit from a big
break.  Don't let this one slip by.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Can I ask you a question ?

[Linda Taylor]

Hey there,



My name’s Linda. Hope you’re doing well right now. I work with Spectral
Core and just wanted to ask you a quick question.



I was browsing your site and noticed mentioned ORM at
https://qa.debian.org/cgi-bin/watch?pkg=doctrine



I find it interesting because we actually have a similar guide on our site.



If you could just take a sec and check out our article about A Case for
ORM, a Case Against ORM, I was hoping you might be able to link to it?



https://www.spectralcore.com/blog/a-case-for-orm-a-case-against-orm/



In return, we can provide you a backlink from one of our partner sites.



Thanks so much,

Linda

P.S. What's the most popular top-level domain in Mordor?



.orc


click here to stop hearing from us



[image: picture] [image: logo]

Can I ask you a question ?

[Linda Taylor]

Hey again

I'd offer to help with your website...



...but it's not really my ‘domain’.



Just checking to see if you’ve had a chance to read my message before. If
you could let me know, it’d be most appreciated.



Hope you’re doing good.


Thanks in advance,

Linda


click here to stop hearing from us
<http://track.healthyeating.club/api/unsubscribe/cam_sNNgBqgF6kGsS9yhm/cGFja2FnZXNAcWEuZGViaWFuLm9yZw==>


On Tue, Mar 16, 2021 4:33 AM, Linda Taylor 
wrote:

> Hey there,
>
>
>
> My name’s Linda. Hope you’re doing well right now. I work with Spectral
> Core and just wanted to ask you a quick question.
>
>
>
> I was browsing your site and noticed mentioned ORM at
> https://qa.debian.org/cgi-bin/watch?pkg=doctrine
>
>
>
> I find it interesting because we actually have a similar guide on our site.
>
>
>
> If you could just take a sec and check out our article about A Case for
> ORM, a Case Against ORM, I was hoping you might be able to link to it?
>
>
>
> https://www.spectralcore.com/blog/a-case-for-orm-a-case-against-orm/
>
>
>
> In return, we can provide you a backlink from one of our partner sites.
>
>
>
> Thanks so much,
>
> Linda
>
> P.S. What's the most popular top-level domain in Mordor?
>
>
>
> .orc
>
>
> click here to stop hearing from us
> <http://track.healthyeating.club/api/unsubscribe/cam_sNNgBqgF6kGsS9yhm/cGFja2FnZXNAcWEuZGViaWFuLm9yZw==>
>
[image: picture] [image: logo]

Can I ask you a question ?

[Linda Taylor]

Hey,



Hope I’m not bugging you. I just wanted to make sure my email doesn’t get
lost in your inbox.

Did you have a chance to check out my email before?



If you’re interested, just let me know.



Thanks so much,

Linda


click here to stop hearing from us
<http://track.healthyeating.club/api/unsubscribe/cam_sNNgBqgF6kGsS9yhm/cGFja2FnZXNAcWEuZGViaWFuLm9yZw==>


On Thu, Apr 8, 2021 10:38 AM, Linda Taylor 
wrote:

> Hey again
>
> I'd offer to help with your website...
>
>
>
> ...but it's not really my ‘domain’.
>
>
>
> Just checking to see if you’ve had a chance to read my message before. If
> you could let me know, it’d be most appreciated.
>
>
>
> Hope you’re doing good.
>
>
> Thanks in advance,
>
> Linda
>
>
> click here to stop hearing from us
> <http://track.healthyeating.club/api/unsubscribe/cam_sNNgBqgF6kGsS9yhm/cGFja2FnZXNAcWEuZGViaWFuLm9yZw==>
> On Tue, Mar 16, 2021 4:33 AM, Linda Taylor 
> wrote:
>
>> Hey there,
>>
>>
>>
>> My name’s Linda. Hope you’re doing well right now. I work with Spectral
>> Core and just wanted to ask you a quick question.
>>
>>
>>
>> I was browsing your site and noticed mentioned ORM at
>> https://qa.debian.org/cgi-bin/watch?pkg=doctrine
>>
>>
>>
>> I find it interesting because we actually have a similar guide on our
>> site.
>>
>>
>>
>> If you could just take a sec and check out our article about A Case for
>> ORM, a Case Against ORM, I was hoping you might be able to link to it?
>>
>>
>>
>> https://www.spectralcore.com/blog/a-case-for-orm-a-case-against-orm/
>>
>>
>>
>> In return, we can provide you a backlink from one of our partner sites.
>>
>>
>>
>> Thanks so much,
>>
>> Linda
>>
>> P.S. What's the most popular top-level domain in Mordor?
>>
>>
>>
>> .orc
>>
>>
>> click here to stop hearing from us
>> <http://track.healthyeating.club/api/unsubscribe/cam_sNNgBqgF6kGsS9yhm/cGFja2FnZXNAcWEuZGViaWFuLm9yZw==>
>>
> [image: picture] [image: logo]