Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New Package: odin-0.10.0
Date: Mon, 10 Jun 2019 23:09:58 +0200	[thread overview]
Message-ID: <20190610210958.uje-3BNu_mXFfOKic19kaPafZgwaiwY0fpEbh33epTU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12322@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/pull/12322#issuecomment-500596048
Comment:
I agree with logenkain. See how I named lbreakouthd. This is it. Sometimes
it's easier. Free choice. Welcome to the humanity

El lun., 10 jun. 2019 22:53, logenkain <notifications@github.com> escribió:

> *@logenkain* commented on this pull request.
> ------------------------------
>
> In srcpkgs/odin/template
> <https://github.com/void-linux/void-packages/pull/12322#discussion_r292186989>
> :
>
> > @@ -0,0 +1,28 @@
> +# Template file for 'odin'
> +pkgname=odin
> +version=0.10.0
> +revision=1
> +archs="x86_64*"
> +wrksrc="Odin-${version}"
>
> Can we get more opinions on this? Back in the day we kinda went either way.
>
> I've always disliked starting a package name with a capital since xbps is
> case sensitive which makes packages harder to deal with. Also, the
> executable itself is lower case, I've always found this to just bring in
> more confusion.
>
> If that's what we do now, that's fine by me (I prefer consistency either
> way) , but I'd like more opinions before I go ahead and make the change.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/12322?email_source=notifications&email_token=AAGR7KIYHHYEIP2Y7FU3HXLPZ25MVA5CNFSM4HWIFUZ2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB3C3V2Y#discussion_r292186989>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAGR7KMUI573UYMNTLBWD2LPZ25MVANCNFSM4HWIFUZQ>
> .
>


  parent reply	other threads:[~2019-06-10 21:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 21:40 [PR PATCH] " voidlinux-github
2019-06-08 23:17 ` voidlinux-github
2019-06-08 23:27 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-08 23:27 ` voidlinux-github
2019-06-08 23:30 ` voidlinux-github
2019-06-08 23:36 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-08 23:36 ` voidlinux-github
2019-06-08 23:37 ` voidlinux-github
2019-06-08 23:51 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-08 23:51 ` voidlinux-github
2019-06-09  0:15 ` voidlinux-github
2019-06-09  0:15 ` voidlinux-github
2019-06-09  0:43 ` voidlinux-github
2019-06-09  2:03 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-09  2:03 ` voidlinux-github
2019-06-09  2:04 ` voidlinux-github
2019-06-09 12:23 ` voidlinux-github
2019-06-09 18:50 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-09 18:50 ` voidlinux-github
2019-06-10 21:09 ` voidlinux-github [this message]
2019-06-12 20:01 ` voidlinux-github
2020-03-24  4:33 ` logenkain
2020-03-24  4:33 ` [PR PATCH] [Closed]: " logenkain

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=20190610210958.uje-3BNu_mXFfOKic19kaPafZgwaiwY0fpEbh33epTU@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).