public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Ignore built files
Date: Wed, 16 Jan 2008 20:17:23 +0100	[thread overview]
Message-ID: <1200511043.7978.65.camel@aeonflux> (raw)
In-Reply-To: <1200498782.26259.41.camel@cookie.hadess.net>

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.

Regards

Marcel



-------------------------------------------------------------------------
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

  reply	other threads:[~2008-01-16 19:17 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 [this message]
2008-01-16 19:28           ` Bastien Nocera
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=1200511043.7978.65.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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