public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] bugfix: isar-exclude-docs delete man folders but some packages expect that folders
Date: Fri, 23 Sep 2022 16:39:44 +0200	[thread overview]
Message-ID: <20220923163944.6a091cb5@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO4DsO9JVHrQ9p2auP67crXKUTz5nFMu+CvE8HhbgjcijQ@mail.gmail.com>

Am Fri, 23 Sep 2022 16:18:12 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:

> Il Ven 23 Set 2022, 14:02 Henning Schild <henning.schild@siemens.com>
> ha scritto:
> 
> >
> > Can you please send the patch with git send-email so it can be
> > reviewed and merged? I think i would make it two patches ... and
> > that switches to "find -type f exec rm", and a second one that
> > switches to "! -type d" ... but both finds not just one.
> >  
> 
> Dear Henning,
> 
>  thanks for the consideration. Unfortunately at the moment, I can just
> attach the file patch to this e-mail. It is the 0001.
> 
>  Plus, I am going to attach other two patches that I have sent in
> this list in the last week. It is the best that I can provide you. If
> not enough, I will try to do something better in the week end.
> 
>  Unfortunately, I gave a company win laptop and I run Linux on a
> unsecure machine on my desktop thus any personal configuration would
> be not acceptable. That's my life for now.

Well yes ... i know all that all too well. I bet if a security expert
looked at your Windows and compared it to that Linux the judgement of
which is less secure might be another than what your IT says.

Any machine on a network where you can smtp to gmail will work, it is
not hard just not so browser-GUI github style easy. I am not sure what
people will do with your attachments. They can not be reviewed as we
are used to, and also not applied as we are used to.

I will take the one that i approved and will take it further. Keeping
you as author, change it a bit and add my signed-off. You will be on CC
for all that. Speak up in case you at some point feel that you do not
want your name as author.

regards,
Henning

>   Best, R-
> 
> > --  
> Roberto A. Foglietta
> +49.176.274.75.661
> +39.349.33.30.697


  reply	other threads:[~2022-09-23 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 20:36 Roberto A. Foglietta
2022-09-22 21:31 ` Roberto A. Foglietta
2022-09-23 12:01   ` Henning Schild
2022-09-23 14:18     ` Roberto A. Foglietta
2022-09-23 14:39       ` Henning Schild [this message]
2022-09-23  8:06 ` Moessbauer, Felix
2022-09-23  9:31   ` Roberto A. Foglietta
2022-09-23 11:18     ` Henning Schild
2022-09-23  8:57 ` Henning Schild
2022-09-23  9:25   ` Henning Schild

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=20220923163944.6a091cb5@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.com \
    /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