Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php on line 14

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_misc.php on line 1621
tag_error <txp:posted format="%a" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/publish.php on line 477
Puntada sin Hilo: Que corra el champán...

Ir al contenido

jue
oct
23

2008

Que corra el champán...

Llega un día en el momento de las personas en el que te levantas pensando en que hay que dar un paso más. Por eso, porque ya es el momento, he decidio renunciar a parte de mi libertad, mutilar mis alas para dejar de volar en solitario y emprender una nueva etapa con grandes cambios y en búsqueda de nuevas situaciones hasta el momento desconocidas. Hoy es ese día para mi.

A partir de ahora todo será diferente, ¿qué me esperará al despertarme cada mañana?. Una rutina que se extingue abre paso a un nuevo periodo de aventuras y desventuras. No sé si podré seguir siendo el mismo, no sé si mi nuevo estatus me obligará a romper con todo lo anterior, no sé si seguiré controlando mi vida o si alguien lo hará por mi... lo único que sé es que tendré que seguir hilando fino y no dar puntada sin hilo.

Que no hombre, sólo es que me voy a casar y no sabía cómo sacar el tema. La mayoría de vosotros ya lo sabías, pero para los que no, a partir del 31 de Mayo del año que viene tendré unas vacaciones más largas de lo habitual y muchos papeles que firmar. Y aprovecho para hacer hincapié en que preparar una boda (al menos una civil) es un poco coñazo... demasiados papeles y vueltas para pocos cambios. Seguro que a lo largo de estos meses me surgirán más cosas que contar.

¡Viva lo novios!

Comentarios

  1. Bueno, la verdad es que no se si decir enhorabuena o… Bueno, como yo no me puedo quejar (más bien todo lo contrario), os felicitaré y desearé lo mejor.

    Por cierto, si piensas que preparar una boda civil es un poco coñazo, no te imaginas una por la iglesia… :)

    Venga… ¡Que se besen, que se besen…!

    Jorge · oct 24, 13:24 · #

  2. ¡¡¡¡¡QUE VIVAN!!!!

    — Lu · oct 25, 11:53 · #

  3. Pues FELICIDADES!!! y …QUE VIVAN LOS NOVIOS!!!!! :-D

    — Terpsicore · oct 26, 20:27 · #

  4. Jesús!

    Creo que me asustaste hasta a mi, y no se si arrepentirme y todo…

    Siempre dije que para mi casarse es una fiesta que celebras junto a los amigos y familiares que quieres y también un recuerdo que es para toda la vida (siempre que no haya que repetir) :P

    Respecto a lo de las alas, atarse y cambiar…. A mí me parece un tópico, creo que después de estos años juntos, ya nos conocemos lo suficiente como para que asumas que, como siempre, te controlo, y que voy a seguir haciéndolo todo lo que pueda y todo lo que tú me dejes, (jaja) y que no hay nada nuevo que pueda sorprenderte como para salir corriendo después del día 31, (salvo cuando me quite por fín las pestañas postizas, la pata de palo, las lentillas de colores y la faja de cuerpo entero que me tiene ahogada durante todos estos años)… :P

    En cuanto a una pareja se que no se puede estar de acuerdo en todo, pero aún así, despues de lo bueno y lo malo que tiene una relación, creo que vale la pena luchar por ella, y estoy de acuerdo contigo en que lo único que nos cambiará el matrimonio serán un montón de papeles por firmar, y un nuevo libro que nos van a dar donde dirá que somos una familia (cosa que a mi me parece muy bonito también,… aunque en él, no nos dejen recoger a nuestro pequeño Saturnino, como hijo adoptado desde hace tres años y que es parte de nuestra modesta familia).

    Lo que tengo claro es que me siento la mujer más feliz y afortunada del mundo por haber podido ver cumplida por fín una de las metas que tenía en mi vida, sino la más importante: convertirme en esposa de uno de los mejores hombres y personas que he conocido.

    La verdad es que para mí, lo más importante, es:

    - Que me siento orgullosa de la persona con quien comparto mi vida y con quien espero seguir haciendolo hasta el fín de la misma, porque ya no puedo imaginarmela sin ti.

    -Y que se que es una suerte que alguien como tú, que me hace ser mejor persona estando a tu lado, me haya elegido como su compañera.

    Besin prometido…

    — NelePh · nov 5, 14:31 · #

  5. Enhorabuena!!!!!!!!

    Por lo que veo has encontrado a alguien tan estupendo como tú. Te lo mereces.

    Vivan los novios!!!!!

    — Begoña · dic 10, 18:55 · #

Ayuda Textile