Linux bluetooth development
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] New keytab storage
Date: Sat, 31 Jan 2004 10:27:14 +0100	[thread overview]
Message-ID: <1075541234.14644.149.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1075511922.3594.49.camel@pegasus>

Hi Marcel

lör 2004-01-31 klockan 02.18 skrev Marcel Holtmann:
> However you should talk a look at libs2 and utils2 from CVS.

I haven't looked closely at libs2 but the hcid parts in utils2 appears
to be a copy of the original utils, except the files are renamed and put
in a "compat" directory with lots of other utilities. Why is that?

A "hcid" directory (as in the old "libs") would be better I think.

> Generate the diffs againt the CVS sources.

Maybe this a FAQ but I only get this:

   $ cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez login
   Logging in to :pserver:anonymous@cvs.bluez.org:2401/cvsroot/bluez
   CVS password:
   cvs [login aborted]: end of file from server (consult above messages if any)
   $

Any hints, please?

> Hope you get my point.

Yes, thanks.

Fredrik

  reply	other threads:[~2004-01-31  9:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 23:56 [Bluez-devel] [PATCH] New keytab storage Fredrik Noring
2004-01-31  0:32 ` Marcel Holtmann
2004-01-31  0:55   ` Fredrik Noring
2004-01-31  1:18     ` Marcel Holtmann
2004-01-31  9:27       ` Fredrik Noring [this message]
2004-01-31 15:23         ` Marcel Holtmann
2004-01-31 15:40           ` Fredrik Noring
2004-01-31 15:52             ` Marcel Holtmann
2004-01-31 16:03               ` Fredrik Noring
2004-01-31 18:01                 ` Marcel Holtmann
2004-01-31 18:15                   ` Fredrik Noring
2004-01-31 10:47   ` Fredrik Noring

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=1075541234.14644.149.camel@akka.yeti.nocrew.org \
    --to=noring@nocrew.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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