linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: bluez installs alsa related stuff under /etc/alsa instead of /usr/share/alsa
Date: Fri, 16 Jul 2010 15:08:18 -0300	[thread overview]
Message-ID: <20100716180817.GA10326@vigoh> (raw)
In-Reply-To: <1279300905.29479.2.camel@localhost.localdomain>

Hi Pacho,

* Pacho Ramos <pacho@condmat1.ciencias.uniovi.es> [2010-07-16 19:21:45 +020=
0]:

> El vie, 16-07-2010 a las 14:01 -0300, Johan Hedberg escribi=F3:
> >=20
> > On Fri, Jul 16, 2010, Pacho Ramos wrote:
> > > Can this be finally committed please? Thanks a lot :-)
> >=20
> > It's strange the the patch has gone unnoticed ever since March. Anyway,
> > could you please provide a git format-patch version of it since that's
> > the convention for all patch submisions. That way I don't need to play
> > manual tricks to get the git author name and email correct for the
> > commit.
> >=20
> > Johan
> >=20
>=20
> Sadly I have always failed to create patches in a git format-patch
> version :'(
>=20
> This is what I have tried:
> $ git clone git://git.kernel.org/pub/scm/bluetooth/bluez.git
> Initialized empty Git repository in /home/pacho/bluez/.git/
> remote: Counting objects: 35451, done.
> remote: Compressing objects: 100% (8577/8577), done.
> remote: Total 35451 (delta 27190), reused 34976 (delta 26858)
> Receiving objects: 100% (35451/35451), 6.16 MiB | 1.39 MiB/s, done.
> Resolving deltas: 100% (27190/27190), done.
> $ cd bluez/
> $ git checkout -b fix_alsa_path
> Switched to a new branch 'fix_alsa_path'
> $ patch -p0
> </usr/portage/net-wireless/bluez/files/bluez-alsa_location.patch=20
> patching file Makefile.am
> Hunk #1 succeeded at 248 (offset 7 lines).
> $ git format-patch master --stdout
> $ (nothing is shown)

If your patch is on HEAD then just do:

git format-patch -1

and then use 'git send-email' to send it to the mailing list.

--=20
Gustavo F. Padovan
http://padovan.org

  reply	other threads:[~2010-07-16 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  8:37 bluez installs alsa related stuff under /etc/alsa instead of /usr/share/alsa Pacho Ramos
2010-03-05  1:42 ` Marcel Holtmann
2010-03-05  9:11   ` Pacho Ramos
2010-03-05  9:24     ` Pacho Ramos
2010-04-10 11:28       ` Pacho Ramos
2010-07-16 10:40         ` Pacho Ramos
2010-07-16 17:01           ` Johan Hedberg
2010-07-16 17:21             ` Pacho Ramos
2010-07-16 18:08               ` Gustavo F. Padovan [this message]
2010-07-16 18:46                 ` Pacho Ramos
2010-07-16 23:44                   ` Johan Hedberg
2010-07-17 14:09                     ` Pacho Ramos

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=20100716180817.GA10326@vigoh \
    --to=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=pacho@condmat1.ciencias.uniovi.es \
    /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;
as well as URLs for NNTP newsgroup(s).