From: Raphael Geissert <atomo64+debian@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] why not using sourceforge's release system?
Date: Sat, 17 Nov 2007 23:39:19 -0600 [thread overview]
Message-ID: <fhoj6b$p47$1@ger.gmane.org> (raw)
Hello,
I was wondering what's the reason sourceforge's mirroring/release system is
not used.
The website service provided sourceforge is not meant to be used for file
storage (read sf.net's documentation, it isn't allowed).
It also makes it hard to implement some monitoring on the file releases by
using a non-standard way.
I would then recommend to switch to sf.net's release/mirroring system.
[Note: I read the list]
Kind regards,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2007-11-18 5:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='fhoj6b$p47$1@ger.gmane.org' \
--to=atomo64+debian@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.