From: patroclo7@gmail.com (Giorgio Lando)
Subject: [sup-talk] [PATCH] Write sup-{exception-log, unable-to-decode}.txt in ~/.sup
Date: Sun, 06 Apr 2008 13:06:55 +0200 [thread overview]
Message-ID: <1207479958-sup-5202@clarabella> (raw)
In-Reply-To: <12072321792626-git-send-email-nicolas.pouillard@gmail.com>
Excerpts from Nicolas Pouillard's message of Thu Apr 03 16:16:19 +0200 2008:
> More precisely new destinations are:
> - ~/.sup/exception-log.txt
> - ~/.sup/unable-to-decode.txt
> This patch avoid some kind of pollution.
I really enjoy this patch, my home folder is now cleaner! Thanks
--
Giorgio Lando <patroclo7 at gmail dot com>
next prev parent reply other threads:[~2008-04-06 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 14:16 Nicolas Pouillard
2008-04-06 11:06 ` Giorgio Lando [this message]
2008-04-21 8:01 ` Nicolas Pouillard
2008-04-23 1:43 ` William Morgan
2008-04-23 8:59 ` Nicolas Pouillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1207479958-sup-5202@clarabella \
--to=patroclo7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox