Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

Blergh... You want it machine readable and I want it human readable. I don't care so much about the cover letter but for the first patch then I really want something minimal (one line) and human readable.

base tree/branch: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master base commit: afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc base patch-id: a849260a843115dbac4b1a330d44256ee6b16d7b base patch-subject: Linux 4.4 base tag: v4.4

To me that looks like an unparseable wall of text. My version of that is:

Applies-to: afd2ff9b7e1b+ origin

As a human all I really want to know is the tree to apply this to. If it doesn't apply then I don't debug it, I just send an automatic note "This doesn't apply to staging-next. Please redo."

I think that Applies-to is a better name and also that grepping for "^base " is less reliable than grepping for ^Applies-to.

I used "origin" because that's the name in Next/Trees. The + means private patches are applied. That's what we already do in naming the kernel. If the + matters, then I would include a cover letter.

I have no idea what a "base patch-id" is so that doesn't work at all.

Including the tag is just duplicative since we already have the hash.

In my email, I proposed that we list all the other private patches in a cover letter, but I think you are saying that we only need to know the most recent private patch? Another idea would be to list them newest to oldest (git log order instead of email order) in the cover letter.

Btw, I always work against linux-next and Dave M is always getting annoyed with me for not marking which patches go to net and which go to net-next. I don't use git format-patch, but I will probably start using "Applies-to: net" or "Applies-to: net-next".

regards, dan carpenter