[Bluez-devel] [PATCH] Ignore built files

[Bluez-devel] [PATCH] Ignore built files

[Bastien Nocera]

Heya,

First "patch" is to add some cvsignore files, cleaning up patches:
http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view

Just untar in the root directory of the checkout. BZ:
http://bugzilla.gnome.org/show_bug.cgi?id=504745

I'd need an opinion on another bug:
http://bugzilla.gnome.org/show_bug.cgi?id=505605

I think that it would be a good idea to move the adapter name to the top
of the dialogue, as it is rather more important than the mode of
operation.

Thoughts?


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

Re: [Bluez-devel] [PATCH] Ignore built files

[Marcel Holtmann]

Hi Bastien,

> First "patch" is to add some cvsignore files, cleaning up patches:
> http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view
> 
> Just untar in the root directory of the checkout. BZ:
> http://bugzilla.gnome.org/show_bug.cgi?id=504745

I never bothered with the .cvsignore stuff, because the way CVS uses it
is totally stupid and calling "make maintainer-clean" will give you a
complete clean repository.

> I'd need an opinion on another bug:
> http://bugzilla.gnome.org/show_bug.cgi?id=505605
> 
> I think that it would be a good idea to move the adapter name to the top
> of the dialogue, as it is rather more important than the mode of
> operation.

Actually I think the mode is more important. You might change your name
once, but the mode change (especially with the visible timeout) is the
one that you use more often.

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

Re: [Bluez-devel] [PATCH] Ignore built files

[Bastien Nocera]

On Wed, 2008-01-16 at 16:32 +0100, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > First "patch" is to add some cvsignore files, cleaning up patches:
> > http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view
> > 
> > Just untar in the root directory of the checkout. BZ:
> > http://bugzilla.gnome.org/show_bug.cgi?id=504745
> 
> I never bothered with the .cvsignore stuff, because the way CVS uses it
> is totally stupid and calling "make maintainer-clean" will give you a
> complete clean repository.

So not going to apply that patch/tarball?

> > I'd need an opinion on another bug:
> > http://bugzilla.gnome.org/show_bug.cgi?id=505605
> > 
> > I think that it would be a good idea to move the adapter name to the top
> > of the dialogue, as it is rather more important than the mode of
> > operation.
> 
> Actually I think the mode is more important. You might change your name
> once, but the mode change (especially with the visible timeout) is the
> one that you use more often.

OK, fair enough.


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

Re: [Bluez-devel] [PATCH] Ignore built files

[Marcel Holtmann]

Hi Bastien,

> > > First "patch" is to add some cvsignore files, cleaning up patches:
> > > http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view
> > > 
> > > Just untar in the root directory of the checkout. BZ:
> > > http://bugzilla.gnome.org/show_bug.cgi?id=504745
> > 
> > I never bothered with the .cvsignore stuff, because the way CVS uses it
> > is totally stupid and calling "make maintainer-clean" will give you a
> > complete clean repository.
> 
> So not going to apply that patch/tarball?

I don't see the need and especially since the long-term goal is to move
to git, it will become useless.

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

Re: [Bluez-devel] [PATCH] Ignore built files

[Bastien Nocera]

On Wed, 2008-01-16 at 16:43 +0100, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > > > First "patch" is to add some cvsignore files, cleaning up patches:
> > > > http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view
> > > > 
> > > > Just untar in the root directory of the checkout. BZ:
> > > > http://bugzilla.gnome.org/show_bug.cgi?id=504745
> > > 
> > > I never bothered with the .cvsignore stuff, because the way CVS uses it
> > > is totally stupid and calling "make maintainer-clean" will give you a
> > > complete clean repository.
> > 
> > So not going to apply that patch/tarball?
> 
> 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...


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

Re: [Bluez-devel] [PATCH] Ignore built files

[Marcel Holtmann]

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

Re: [Bluez-devel] [PATCH] Ignore built files

[Bastien Nocera]

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

Re: [Bluez-devel] [PATCH] Ignore built files

[Marcel Holtmann]

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.

for me it really boils down to the SCM in the end. I am not a big fan of
CVS, but switching to SVN is not an option. Best would be if GNOME would
support GIT, because then we can switch right now.

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

Re: [Bluez-devel] [PATCH] Ignore built files

[Jaap A. Haitsma]

On Jan 16, 2008 8:47 PM, Marcel Holtmann <marcel@holtmann.org> 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.
>
> for me it really boils down to the SCM in the end. I am not a big fan of
> CVS, but switching to SVN is not an option. Best would be if GNOME would
> support GIT, because then we can switch right now.
>
Marcel,

You can use git-svn on SVN repositories to get almost full git
functionality [1]. Quite some GNOME developers already use that for
modules in GNOME SVN.

Jaap

[1] http://live.gnome.org/GitForGnomeDevelopers

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