Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] No top-level directory in tarballs
Date: Sun, 29 Dec 2019 13:22:19 +0100 (CET)	[thread overview]
Message-ID: <20191229122219.5DF11F8014F@alsa1.perex.cz> (raw)
In-Reply-To: <1577622135498452902-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #10 was opened from tanuk:

Usually release tarballs have a top-level directory in the format "&lt;packagename>-&lt;version>". At least the 1.2.1.2 release of alsa-ucm-conf didn't have any such directory, which caused some headache for me as a packager. I figured out how to deal with it, so I don't need this issue fixed, but it would probably still be a good idea to add the conventional directory in future releases.

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/10
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

           reply	other threads:[~2019-12-29 12:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1577622135498452902-webhooks-bot@alsa-project.org>]

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=20191229122219.5DF11F8014F@alsa1.perex.cz \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.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