From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Ignore built files
Date: Wed, 16 Jan 2008 19:28:15 +0000 [thread overview]
Message-ID: <1200511695.26259.56.camel@cookie.hadess.net> (raw)
In-Reply-To: <1200511043.7978.65.camel@aeonflux>
On Wed, 2008-01-16 at 20:17 +0100, Marcel Holtmann wrote:
> Hi Bastien,
>
> > > I don't see the need and especially since the long-term goal is to move
> > > to git, it will become useless.
> >
> > I thought we wanted to move bluez-gnome to GNOME's SVN...
>
> personally I think that Subversion is as worse as CVS and I don't see
> any advantage for a switch to that. Convincing me that GNOME's
> infrastructure makes sense is different, but from a pure technical
> standpoint of the SCM, Subversion is not an argument I am gonna buy
> into.
I'm not getting into SCM discussions, if GNOME was still using CVS, I'd
still be using CVS (and so forth). What I meant was using the GNOME
infrastructure to get translators, documentation writers, and plenty of
pairs of eyeballs for the code.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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
next prev parent reply other threads:[~2008-01-16 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 13:15 [Bluez-devel] [PATCH] Ignore built files Bastien Nocera
2008-01-16 15:32 ` Marcel Holtmann
2008-01-16 15:35 ` Bastien Nocera
2008-01-16 15:43 ` Marcel Holtmann
2008-01-16 15:53 ` Bastien Nocera
2008-01-16 19:17 ` Marcel Holtmann
2008-01-16 19:28 ` Bastien Nocera [this message]
2008-01-16 19:47 ` Marcel Holtmann
2008-01-16 21:29 ` Jaap A. Haitsma
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=1200511695.26259.56.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox