From: theinicke@bss-wf.de
To: 9front@9front.org
Subject: Re: [9front] [PATCH] hgignore: ignore arm64 binaries and bcm/bcm64 kernels
Date: Fri, 6 Mar 2020 21:14:46 +0100 [thread overview]
Message-ID: <608E7E625725E10FD84FD2C89FE6B745@yourdomain.dom> (raw)
In-Reply-To: <A2C16D3CED30A66EE23991436002537D@felloff.net>
> good point... i think we can even use s?9.* to match the kernels. [...]
While we are at it, we might include downloadable firmware:
hgignore: ignore arm64 binaries, arm kernels and firmware
- ignore arm64 binaries
- ignore arm/arm64 kernels and init
- ignore downloaded raspberry pi firmware files
diff -r 0dd419f096e2 .hgignore
--- a/.hgignore Sun Mar 01 23:23:01 2020 +0100
+++ b/.hgignore Fri Mar 06 21:12:25 2020 +0100
@@ -1,11 +1,13 @@
syntax: regexp
-^(386|68000|68020|alpha|amd64|arm|mips|power|power64|sparc|sparc64|spim)/(bin|lib)(/|$)
+^(386|68000|68020|alpha|amd64|arm|arm64|mips|power|power64|sparc|sparc64|spim)/(bin|lib)(/|$)
^(acme|sys/src)/(.*/)?[0125678vqki]\..*$
^(acme|sys/src)/.*\.[ao]?[0125678vqki]?$
^(dev|fd|net.*|srv|shr|env|root|proc|boot|mnt|n|bin|usr|cfg|cron|mail|tmp)(/|$)
^386/(9(pc|boot).*|pbs|mbr|init)
^amd64/(9pc64|init)
-^acme/bin/(386|68000|68020|alpha|amd64|arm|mips|power|power64|sparc|sparc64|spim)(/|$)
+^arm/(s?9.*|init)
+^arm64/(s?9.*|init)
+^acme/bin/(386|68000|68020|alpha|amd64|arm|arm64|mips|power|power64|sparc|sparc64|spim)(/|$)
^adm/(cache|keys|netkeys|secstore|users|whois|timezone/local)(/|$)
^lib/(ndb|audio|firmware)(/|$)
^lib/rfc/(drafts|index|rfc.*)(/|$)
@@ -15,4 +17,5 @@
^sys/log(/|$)
^sys/man/(searchindex|[1-8]/INDEX.*)$
^sys/src/.*\.(bits|debug|output|tab\.[hc])$
+^sys/src/boot/bcm/.*\.(bin|broadcom|dat|dtb|elf)$
^sys/src/pkg(/|$)
prev parent reply other threads:[~2020-03-06 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 8:42 theinicke
2020-03-05 19:09 ` [9front] " cinap_lenrek
2020-03-06 20:14 ` theinicke [this message]
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=608E7E625725E10FD84FD2C89FE6B745@yourdomain.dom \
--to=theinicke@bss-wf.de \
--cc=9front@9front.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).