mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Lord <lord@regexps.com>
To: linux-kernel@vger.kernel.org
Subject: a new arch feature "for Linus"
Date: Sun, 10 Feb 2002 01:13:15 -0800 (PST)	[thread overview]
Message-ID: <200202100913.BAA29987@morrowfield.home> (raw)


Not really only for Linus, but inspired by a feature he requested 
of Bitkeeper on this list a few weeks ago.

The command is:

	  % arch touched-files-prereqs REVISION

That command looks at the patch set for REVISION and at all preceding
patch sets in the same version (aka "Line of Development"[1]).  It
reports the list of patches that touch overlapping sets of files and
directories -- in other words, it tells you what patches can be
applied independently of others (from "linear" to "bushy" patch sets).
The command has an option to exclude from consideration file names
matching a certain pattern (e.g. "=README" or "ChangeLog").  It has an
option to exclude from the output list patches which have already been
applied to a given project tree.  It has an option to report the
specific files which are overlapped.

Linus actually asked for something slightly more precise: beyond
looking at whether two patch sets modify the same files, he wants to
know if they specifically modify overlapping sections of those files.  
I haven't implemented that yet but it's certainly doable.
(`touched-files-prereqs' is 297 lines long; delving into the patch
details will likely more than double that.)

We now return you to your previously scheduled Bitkeeper product
placement advertisement.

Pepsi adds life!,
-t

[1] "Lines of Development" is a trademark of BitMover, Inc.


             reply	other threads:[~2002-02-10  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10  9:13 Tom Lord [this message]
2002-02-10  9:53 ` Russell King
2002-02-10 18:27 ` Tom Lord
2002-02-11 12:55 ` Pavel Machek
2002-02-11 22:45 ` Tom Lord
2002-02-11 19:59   ` Ahmed Masud

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=200202100913.BAA29987@morrowfield.home \
    --to=lord@regexps.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®