public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 0/4] apt configuration fixes
Date: Mon, 21 Feb 2022 19:24:56 +0100	[thread overview]
Message-ID: <20220221192456.1a9414b2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <YhPC+Z3wArV8eoi4@ilbers.de>

Am Mon, 21 Feb 2022 17:51:05 +0100
schrieb Baurzhan Ismagulov <ibr@radix50.net>:

> On Mon, Feb 21, 2022 at 05:12:55PM +0100, Henning Schild wrote:
> > 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>"
> > 
> > Please let me know if a force-push is possible, i would prepare a
> > "next" on github for a hard reset.  
> 
> Fixed, please check.
> 
> In general, I'd like to avoid rewriting history because it's, well,
> history :) .

Thanks a million! I know that history rewriting is bad and isar usually
does not do it ... even on "next" where other projects might be more
relaxed about it.

I sure hope it does not happen again and it would be asking too much
for the maintainer to maybe double-check. But if anyone sees a "weird"
"From" just speak up and ask the contributor to check their mail setup.

I personally would do my best to deliver patches again and try to help
people to fix such issues (especially those trying to send From
@siemens.com). 

regards,
Henning

> With kind regards,
> Baurzhan.
> 


  reply	other threads:[~2022-02-21 18:25 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 [this message]
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

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=20220221192456.1a9414b2@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=ibr@radix50.net \
    --cc=isar-users@googlegroups.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