public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3] debianize: Add placeholder for original version to CHANGELOG_V
Date: Fri, 8 May 2020 08:02:52 +0200	[thread overview]
Message-ID: <20200508060252.gsbrpsxhdij45ytz@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200508074505.16c67b3c@md1za8fc.ad001.siemens.net>

On Fri, May 08, 2020 at 07:45:05AM +0200, Henning Schild wrote:
> > Oops, I haven't seen the intention to do that, have I overlooked
> > anything? I've stated the reason in the next mail -- sorry for
> > one-side decision. If there is consensus on a working approach, I'd
> > of course welcome that.
> 
> It was hard to see. The follow up kind of questions this series and the
> discussion is still ongoing.
> 
> > > Not sure how to deal with the premature merge now.  
> > 
> > The final solution can be applied on top, or I can revert the patches
> > if that would help.
> 
> The feature will potentially vanish or work differently. That should be
> clear for users. Since isar master is slow many users are on next. Next
> does not seem to ever rebase.
> So i say we need to finish the discussion eventually. Until then
> potentially revert the commits to prevent users jumping on a feature
> that will be harder to repair once its out there.
> 
> Let us see what Jan has to say. Maybe the discussion only seems open
> because the points i raised are not valid in his opinion.

I see, thanks for the explanations. IMHO, your points are perfectly valid and
addressing them would be a good structural improvement. OTOH, Jan's use case
doesn't go away, and his change works as is. But I agree we should finish the
discussion.


With kind regards,
Baurzhan.

  reply	other threads:[~2020-05-08  6:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 16:31 Jan Kiszka
2020-04-23 16:43 ` Henning Schild
2020-04-23 16:50   ` Jan Kiszka
2020-04-23 17:32     ` Henning Schild
2020-04-24  7:59       ` Jan Kiszka
2020-04-23 16:47 ` Henning Schild
2020-05-07 19:45 ` Baurzhan Ismagulov
2020-05-07 20:02   ` Henning Schild
2020-05-07 20:28     ` Baurzhan Ismagulov
2020-05-08  5:45       ` Henning Schild
2020-05-08  6:02         ` Baurzhan Ismagulov [this message]
2020-05-08  6:02     ` Jan Kiszka
2020-05-08  6:06       ` Baurzhan Ismagulov

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=20200508060252.gsbrpsxhdij45ytz@yssyq.m.ilbers.de \
    --to=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