All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: emufxtool, formerly ld10k1
Date: Wed, 30 Jul 2003 20:25:35 +0200	[thread overview]
Message-ID: <s5hoezbrhwg.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030730200408.6a9e12fe.nigu@itadinanta.it>

At Wed, 30 Jul 2003 20:04:08 +0200,
Nicola Orru' wrote:
> 
> > > May I have a pointer to a page (I'll RTFM!) that contains the
> > > "protocol" to apply when working on alsa cvs, to create, pack and
> > > send patches to maintainers? 
> >  
> > yes, documentation is always nice :)
> 
> Humm. I'm Sorry :(
> 
> I suppose I did not express myself clearly  :P. 
> 
> I don't know how to access that information, I would like to get it in some way. In a word: can you send me a link to the docs?

oh, sorry, i misread the sentence above.

well, there is no protocol for that.
so far, cvs write access is limited to ALSA core developers.

i'll need to integrate the whole emufxtool tree to alsa-tools cvs tree
(after modified to suit with the alsa-tools tree) at first.  after
that, you can get them from anon cvs.

once after the tree is there, you can make easily patches via cvs
diff.  then please send me or Jaroslav (or alsa-devel ML) the patch,
so we'll commit it soon.

if you'd like to keep the different cvs tree on sf, go ahead.
please give us the patch sometimes to keep the trees in sync.


so, the first step is to make a final tarball for inclusion.
as already mentioned, it's better to have GPL notes in each file, and
have configure stuffs.
if these changes are finished, please let me know the URL (or send me
the tarball).  i'll merge it to alsa-tools tree ASAP.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

  reply	other threads:[~2003-07-30 18:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 15:41 emufxtool, formerly ld10k1 Nicola Orru'
2003-07-30 15:55 ` Takashi Iwai
2003-07-30 16:14 ` Takashi Iwai
2003-07-30 16:21 ` Takashi Iwai
     [not found]   ` <20030730185508.3f9eac3d.nigu@itadinanta.it>
     [not found]     ` <s5hr848q74h.wl@alsa2.suse.de>
     [not found]       ` <20030730192029.792cd48d.nigu@itadinanta.it>
2003-07-30 17:26         ` Takashi Iwai
2003-07-30 18:04           ` Nicola Orru'
2003-07-30 18:25             ` Takashi Iwai [this message]
2003-07-30 18:47               ` Jaroslav Kysela
2003-07-30 19:10                 ` Jaroslav Kysela
2003-07-30 20:53                   ` Nicola Orru'
2003-07-30 21:50                     ` Nicola Orru'
2003-08-05 13:40                       ` Takashi Iwai
2003-08-07 19:33                         ` Nicola Orru'
  -- strict thread matches above, loose matches on Subject: below --
2003-08-11 10:42 p z oooo

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=s5hoezbrhwg.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-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.