Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jordi Mallach <jordi@debian.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Debian patches for ALSA
Date: Sat, 11 May 2013 18:16:25 +0400	[thread overview]
Message-ID: <20130511141625.GZ3200@sirena.org.uk> (raw)
In-Reply-To: <1368225163.24178.1.camel@penyagolosa.oskuro.net>


[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]

On Sat, May 11, 2013 at 12:32:43AM +0200, Jordi Mallach wrote:

> I'm going to outline all the individual patches below. The patch tracker
> has the patches just as I would send them upstream, but if you prefer
> git formatted patches, I can go ahead and do that too, if it makes your
> life easier.

That's the normal workflow for sending stuff and it makes it easy to
apply things.

> http://patch-tracker.debian.org/patch/series/view/alsa-tools/1.0.27-2/envy24control_config_dir.patch
>    This one is to be discussed. envy24control currently creates a
> visible directory in $HOME, which is quite unacceptable. This patch just
> moves the directory to a dotdir, but an upgrade path might need to be
> coded. I would just move the thing away.

Or just have it only create the .dir but check both names?

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2013-05-11 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 22:32 Debian patches for ALSA Jordi Mallach
2013-05-11 14:16 ` Mark Brown [this message]
2013-05-13  7:12 ` Jaroslav Kysela
2013-05-14 23:04   ` Jordi Mallach

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=20130511141625.GZ3200@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jordi@debian.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