public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Anton Mikanovich <amikan@ilbers.de>,
	<isar-users@googlegroups.com>,
	Srinuvasan A <srinuvasan_a@mentor.com>,
	vijai kumar <vijaikumar.kanagarajan@gmail.com>,
	Gernot Hillier <gernot.hillier@siemens.com>,
	"Bezdeka, Florian" <florian.bezdeka@siemens.com>
Subject: Re: [PATCH 0/4] apt configuration fixes
Date: Tue, 22 Feb 2022 10:06:32 +0100	[thread overview]
Message-ID: <eab738d8-d862-b9b3-37c9-3adccba41c3a@siemens.com> (raw)
In-Reply-To: <20220221213029.6d1f1ccc@md1za8fc.ad001.siemens.net>

On 21.02.22 21:30, Henning Schild wrote:
> Am Mon, 21 Feb 2022 20:20:21 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 21.02.22 17:12, Henning Schild wrote:
>>> Am Mon, 21 Feb 2022 12:24:09 +0300
>>> schrieb Anton Mikanovich <amikan@ilbers.de>:
>>>   
>>>> 5.02.22 18:15, henning.schild@siemens.com wrote:  
>>>>> This attempts to solve the apt fetch retry problem in a better
>>>>> way. On the way it was found that bootstrap leaves a file around,
>>>>> which probably should not remain in images.
>>>>>
>>>>> Henning Schild (4):
>>>>>    rootfs: configure apt to always retry downloads
>>>>>    Revert "deb-dl-dir: Retry downloads 3 times for src files"
>>>>>    Revert "rootfs: Retry downloads 3 times"
>>>>>    bootstrap: do not leave 50isar.conf in final rootfss
>>>>>
>>>>>   meta/classes/deb-dl-dir.bbclass                |  2 +-
>>>>>   meta/classes/image.bbclass                     |  1 +
>>>>>   meta/classes/rootfs.bbclass                    | 18
>>>>> +++++++++++++++++- .../isar-bootstrap/files/isar-apt.conf
>>>>> | 2 -- .../isar-bootstrap/isar-bootstrap.inc          |  5 +----
>>>>>   5 files changed, 20 insertions(+), 8 deletions(-)
>>>>>   delete mode 100644
>>>>> meta/recipes-core/isar-bootstrap/files/isar-apt.conf   
>>>> Applied to next, thanks.
>>>>  
>>>
>>> Thanks! I see only now that the "From:" in my emails was messed
>>> with by the SMTP server i am now forced to use. Any chance we can
>>> force-push next to fix that?
>>>
>>> What i did send and wanted was 
>>> "Henning Schild <henning.schild@siemens.com>" but what came out is
>>> "henning.schild@siemens.com <henning.schild@siemens.com>"
>>>   
>>
>> I heard these complaints from other as well. Since our servers started
>> rewriting but also because of me sometime using different servers, I
>> *always* force git to inject a From: line into the commit messages.
>> That makes you independent of those manglings.
> 
> How do you force git? I am using my own force since a couple of years
> ... not sure why it failed this time.
> 
> https://github.com/henning-schild/git/commit/ca44f026a31537477e66559f0bf0f3acd2deecdf
> 
> I should probably go ahead and mainline that or something similar.

git format-patch --form="bla"
  -> adds "From:" to body (unless you committed as "bla")
git send-email --from="real@user.com"

> 
>> BTW, my local maintainer tool tries to detect such cases, at least
>> when there is also a signed-off line, and that one differs from the
>> author's line.
> 
> Maybe such a tool should not remain "local", but really it should not
> be required if mail servers would simply send what they are told to.

https://addons.thunderbird.net/de/thunderbird/addon/copy-patch/

Jan

> 
> In fact i will likely switch to sending from "@hennsch.de" soon, not
> caring anymore.
> 
> regards,
> Henning
> 
>> Jan
>>
> 

-- 
Siemens AG, Technology
Competence Center Embedded Linux

      parent reply	other threads:[~2022-02-22  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 15:15 henning.schild
2022-02-05 15:15 ` [PATCH 1/4] rootfs: configure apt to always retry downloads henning.schild
2022-02-05 15:15 ` [PATCH 2/4] Revert "deb-dl-dir: Retry downloads 3 times for src files" henning.schild
2022-02-05 15:15 ` [PATCH 3/4] Revert "rootfs: Retry downloads 3 times" henning.schild
2022-02-05 15:15 ` [PATCH 4/4] bootstrap: do not leave 50isar.conf in final rootfss henning.schild
2022-02-05 15:18 ` [PATCH 0/4] apt configuration fixes Henning Schild
2022-02-21  9:24 ` Anton Mikanovich
2022-02-21 16:12   ` Henning Schild
2022-02-21 16:51     ` Baurzhan Ismagulov
2022-02-21 18:24       ` Henning Schild
2022-02-21 19:20     ` Jan Kiszka
2022-02-21 20:30       ` Henning Schild
2022-02-22  9:01         ` Bezdeka, Florian
2022-02-22  9:06         ` Jan Kiszka [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=eab738d8-d862-b9b3-37c9-3adccba41c3a@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=florian.bezdeka@siemens.com \
    --cc=gernot.hillier@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasan_a@mentor.com \
    --cc=vijaikumar.kanagarajan@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