All of lore.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] CVS access ?
Date: Mon, 25 Sep 2006 23:53:51 +0200	[thread overview]
Message-ID: <1159221231.20997.31.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.63.0609181651370.7570@redbean.intranet.gw-instruments.de>

Hi Peter,

> > > may be I'm only stupid, but I can noot get anything from the CVS as 
> > > published on www.bluez.org. 
> > 
> > you are doing nothing wrong, but the kernel repository got cleared a
> > long time ago. We are not using it anymore.
> 
> So the stuff from kernel.org is assumed to be the most recent version (or, 
> if available, the latest .mh patch), right ? 

the kernel.org stuff is what will go into upstream. The -mh patch also
contains development stuff that might break or isn't fully testing at
the moment.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-09-25 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 13:51 [Bluez-devel] CVS access ? Peter Wippich
2006-09-18 14:20 ` Marcel Holtmann
2006-09-18 14:55   ` Peter Wippich
2006-09-25 21:53     ` Marcel Holtmann [this message]

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=1159221231.20997.31.camel@localhost \
    --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 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.