All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Owen Hilyard <ohilyard@iol.unh.edu>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"Lijuan Tu" <lijuan.tu@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v1 1/2] git: ignore standard python files
Date: Fri, 4 Nov 2022 09:16:00 +0000	[thread overview]
Message-ID: <00eea40ab0bb433abe673513b21ca76b@pantheon.tech> (raw)
In-Reply-To: <20221103132926.445627-2-juraj.linkes@pantheon.tech>

Adding folks I forgot to add

> -----Original Message-----
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Sent: Thursday, November 3, 2022 2:29 PM
> Cc: dev@dpdk.org; Juraj Linkeš <juraj.linkes@pantheon.tech>
> Subject: [PATCH v1 1/2] git: ignore standard python files
> 
> These are python byte-compiled/optimized/dll files and IDE files.
> 
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> ---
>  .gitignore | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/.gitignore b/.gitignore
> index 212c7aa28e..fbec0ce441 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -33,8 +33,10 @@ GRTAGS
>  tags
>  TAGS
> 
> -# ignore python bytecode files
> -*.pyc
> +# python byte-compiled/optimized/dll files __pycache__/ *.py[cod]
> +*$py.class
> 
>  # ignore default build directory, and directories from test-meson-builds.sh
> build
> --
> 2.30.2


  reply	other threads:[~2022-11-04  9:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 13:29 [PATCH v1 0/2] python gitignore and line length Juraj Linkeš
2022-11-03 13:29 ` [PATCH v1 1/2] git: ignore standard python files Juraj Linkeš
2022-11-04  9:16   ` Juraj Linkeš [this message]
2022-11-04  9:26   ` Bruce Richardson
2023-07-16 18:11   ` [PATCH] doc: fix description of runtime directories Stephen Hemminger
2023-07-20  3:26     ` Thomas Monjalon
2022-11-03 13:29 ` [PATCH v1 2/2] doc: increase python max line to 88 Juraj Linkeš
2022-11-04  9:16   ` Juraj Linkeš
2022-11-04  9:28     ` Bruce Richardson
2022-11-04 16:57     ` Stephen Hemminger
2022-11-10  9:15       ` Juraj Linkeš
2022-11-10 16:27         ` Stephen Hemminger
2023-09-26 12:10   ` [PATCH v2 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-09-26 12:10     ` [PATCH v2 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-09-26 21:52       ` Jeremy Spewock
2023-09-28  7:27         ` Juraj Linkeš
2023-09-27  8:08       ` Bruce Richardson
2023-09-28  7:33         ` Juraj Linkeš
2023-09-28  8:42           ` Bruce Richardson
2023-09-26 13:00     ` [PATCH v2 1/2] doc: increase python max line length to 100 Bruce Richardson
2023-09-28 12:18     ` [PATCH v3 " Juraj Linkeš
2023-09-28 12:18       ` [PATCH v3 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-09-29 16:53         ` Jeremy Spewock
2023-10-13  7:58         ` [PATCH v4 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-10-13  7:58           ` [PATCH v4 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-10-16  6:45             ` [PATCH v5 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-10-16  6:45               ` [PATCH v5 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-11-20 12:36                 ` [PATCH v6 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-11-20 12:36                   ` [PATCH v6 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-11-20 16:50                     ` Thomas Monjalon
2023-11-21  9:27                       ` Juraj Linkeš
2023-10-13 16:09           ` [PATCH v4 1/2] doc: increase python max line length to 100 Stephen Hemminger
2023-10-16  6:44             ` Juraj Linkeš
2023-10-12 12:52       ` [PATCH v3 " Paul Szczepanek
2023-10-13  7:56         ` Juraj Linkeš
2022-11-04  9:15 ` [PATCH v1 0/2] python gitignore and line length Juraj Linkeš

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=00eea40ab0bb433abe673513b21ca76b@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.