Thread (13 messages) 13 messages, 5 authors, 2016-06-15

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

flat view

From: Eric Miao <hidden>
Date: 2016-06-15 22:55:12

On Mon, Nov 5, 2012 at 10:40 PM, Michael J Gruber
[off-list ref] wrote:
Eric Miao venit, vidit, dixit 05.11.2012 15:12:
quoted
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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help