Re: Finding changes in one branch not in two other branch

"Aneesh Kumar" [off-list ref] writes:

To show a workflow:

kernel releases 2.6.20 and the project release patchset on top of 2.6.20
kernel release 2.6.21 and project release patchset on top of 2.6.21

The second release involve some bug fixes for the project.

The intention is to find out what changed in project with the release of
2.6.21 patchset

That depends on your definition of what a patchset is.

If it is a set of files, each file has a patch to one or more files to
implement a logically independent and complete change (i.e. corresponds to
what a commit should be), then you can run git-patch-id on each of them to
find the duplicates in these two sets (you do not need a git repository to
do this, as patch-id is a freestanding operation).

If you mean a single file that contains the difference between the vanilla
2.6.21 and their version, then you cannot do much better than running
interdiff, I'd guess.