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.
On Sun, Feb 10, 2002 at 01:13:15AM -0800, Tom Lord wrote:
> 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
'arch' really isn't a good choice of command name:
$ which arch
/bin/arch
$ man arch
ARCH(1) Linux Programmer's Manual ARCH(1)
NAME
arch - print machine architecture
--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
> The command is:
>
> % arch touched-files-prereqs REVISION
'arch' really isn't a good choice of command name:
Not it isn't. But the announcment I cut and pasted the example from is
out of date. In 1.0pre7 the command has been renamed "larch". The
command is really:
> % larch touched-files-prereqs REVISION
Also in the latest NEWS file and worth mentioning since some kernel
maintainers have complained:
* NOT DONE IN THIS RELEASE, BUT MUCH REQUESTED AND LIKELY TO HAPPEN
The directory "{arch}" in project trees should, at least optionally,
have a different name -- but this is slightly tricky to do in an
upward compatible way so I'm putting it off for now.
-t
Hi!
> [1] "Lines of Development" is a trademark of BitMover, Inc.
Is this joke or serious?
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
It's true, to the best of my knowledge.
-t
Date: Mon, 11 Feb 2002 12:55:08 +0000
From: Pavel Machek <[email protected]>
Cc: [email protected]
Content-Type: text/plain; charset=us-ascii
X-UIDL: dda5f09a906d84e75abb5b2582204cb3
Hi!
> [1] "Lines of Development" is a trademark of BitMover, Inc.
Is this joke or serious?
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
On Mon, 11 Feb 2002, Tom Lord wrote:
>
>
> It's true, to the best of my knowledge.
>
> -t
>
>
>
> Date: Mon, 11 Feb 2002 12:55:08 +0000
> From: Pavel Machek <[email protected]>
> Cc: [email protected]
> Content-Type: text/plain; charset=us-ascii
> X-UIDL: dda5f09a906d84e75abb5b2582204cb3
>
> Hi!
>
> > [1] "Lines of Development" is a trademark of BitMover, Inc.
>
> Is this joke or serious?
Even if Lines of Development is a trademark, it is only a trademark in a
particular context. Using it elsewhere, so long as there is no ambiguity
with the description of the Art in the trademark application is okay and
does not violate the trademark.
- A.