linux-kernel - Re: [RFC] to rebase or not to rebase on linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 24 Oct 2009 14:51:31 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	rostedt@...dmis.org
CC:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Nicolas Pitre <nico@...xnic.net>,
	"Luck, Tony" <tony.luck@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	Jeff Garzik <jeff@...zik.org>,
	Robert Richter <robert.richter@....com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jean Delvare <khali@...ux-fr.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC] to rebase or not to rebase on linux-next

Steven Rostedt wrote:
> Some of the reasons for the constant rebasing are:
> 
> 1) the patches are held in quilt, which just by nature leads to
> rebasing.  These developers find that quilt is the best tool for the
> job.

It shouldn't be difficult to implement a git-quiltimport porcelain which
  - remembers a previous import of a quilt tree,
  - compares that one ( = an existing branch) with a new quilt import
    ( = a new branch),
  - reuses all commits of the old import which have identical diffs/
    changelog/ authorship/ parent changeset as ones in the new import,
  - discards (or reverts?) commits of the old import that don't match
    the new import in this way,
  - finally rebases all remaining commits from the new import onto the
    kept old ones.

[OTOH the whole discussion is not about stable SHA1s in linux-next per
se, AFAIU, but about stability of (the history of) the code which is
released into linux-next, or about misuse of linux-next for more than
final integration-testing...?]
-- 
Stefan Richter
-=====-==--= =-=- ==---
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/