From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] Distribution kernel bugzillas considered harmful
Date: Wed, 05 Sep 2018 20:40:28 +0100 [thread overview]
Message-ID: <1536176428.3627.28.camel@HansenPartnership.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1809052119580.15880@cbobk.fhfr.pm>
On Wed, 2018-09-05 at 21:25 +0200, Jiri Kosina wrote:
> On Wed, 5 Sep 2018, James Bottomley wrote:
>
> > We do this in SCSI as well, but only if the tree hasn't yet been
> > submitted to Linus. The technical term is folding. It's
> > obviously better to fix buggy commits that haven't gone upstream
> > because it improves bisectability.
>
> We are drifting away a bit here, but now that you have mentioned it,
> let me add a datapoint to this -- it's actually causing issues to
> our workflow, as we have scsi.git as one of the upstreams [1], and
> when you rebase, it blows up our git workflow and we have to fixup
> things manually.
Describe the issues and we'll try to come up with a fix, but on the
whole you should regard the scsi trees somewhat similarly to linux-
next: it's our proposal for a patch set but we may update it.
> So if you are aware of your tree having downstreams, and care about
> not breaking them and want to be nice to them, you shouldn't rebase
> that tree [2].
Well, I wasn't aware of this one, but I'm sure we can come up with a
functional workflow once I understand what's happening with the
downstream tree.
James
> [1] there are some funny technical details, but in basic principle
> it's exactly like that
>
> [2] https://yarchive.net/comp/linux/git_rebase.html
>
> Thanks,
>
next prev parent reply other threads:[~2018-09-05 19:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 10:13 James Bottomley
2018-09-05 11:37 ` Mark Brown
2018-09-05 15:03 ` Paul E. McKenney
2018-09-05 15:50 ` Steven Rostedt
2018-09-05 16:20 ` Paul E. McKenney
2018-09-05 16:45 ` James Bottomley
2018-09-05 17:00 ` Paul E. McKenney
2018-09-05 19:25 ` Jiri Kosina
2018-09-05 19:40 ` James Bottomley [this message]
2018-09-06 19:54 ` Jiri Kosina
2018-09-18 13:43 ` Martin K. Petersen
2018-09-18 14:12 ` Geert Uytterhoeven
2018-09-18 15:01 ` Martin K. Petersen
2018-09-18 15:27 ` Christoph Hellwig
2018-09-18 15:34 ` Jens Axboe
2018-09-18 17:08 ` Mark Brown
2018-09-18 16:12 ` Mark Brown
2018-09-18 20:20 ` Takashi Iwai
2018-09-19 0:08 ` Mark Brown
2018-09-18 20:37 ` Takashi Iwai
2018-09-19 6:16 ` Geert Uytterhoeven
2018-09-19 6:31 ` Takashi Iwai
2018-09-19 9:23 ` Jan Kara
2018-09-19 9:27 ` Takashi Iwai
2018-09-05 13:16 ` Takashi Iwai
2018-09-05 13:20 ` Jiri Kosina
2018-09-05 13:39 ` Konstantin Ryabitsev
2018-09-05 15:16 ` Sasha Levin
2018-09-05 16:44 ` Laura Abbott
2018-09-05 20:15 ` Konstantin Ryabitsev
2018-09-05 20:36 ` Takashi Iwai
2018-09-07 20:24 ` Mauro Carvalho Chehab
2018-09-05 17:41 ` Laura Abbott
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=1536176428.3627.28.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jikos@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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