Re: Support for a series of patches, i.e. patchset or changeset?

From: Eric Miao <eric.y.miao@gmail.com>
Date: Nov 6, 2012, 00:58 UTC
Message-ID: <CAMPhdO-Z3E352KbTvnrxJqCecAUGfHCwOoFRUKzObh35uLnrSw@mail.gmail.com>
In-Reply-To: <5097CFCB.7090506@drmicha.warpmail.net>

On Mon, Nov 5, 2012 at 10:40 PM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

Show 9 quoted lines

> Eric Miao venit, vidit, dixit 05.11.2012 15:12:
>> The problem is, most cases we have no idea of the base rev1, and commit rev2
>> which it's leading up to. E.g. for a single patch which is between
>> commit rev1..rev2,
>> how do we find out rev1 and rev2.
>
> So, then the question is: What do you know/have? Is your patch the
> output of "git format-patch", "git diff", or just some sort of diff
> without any git information?

That doesn't matter, all the info can be obtained from the SHA1 id, the question is: do we have a mechanism in git (or hopefully we could add) to record the patchset or series the patch belongs to, without people to guess heuristically.

E.g. when we merged a series of patches:

  [PATCH 00/08]
  [PATCH 01/08]
  ...
  [PATCH 08/08]

How do we know this whole series after merged when only one of these commits are known?