Message ID | alpine.LFD.2.00.1104291544410.28705@right.am.freescale.net |
---|---|
State | Accepted |
Delegated to: | Kumar Gala |
Headers | show |
Dear Kumar Gala, In message <alpine.LFD.2.00.1104291544410.28705@right.am.freescale.net> you wrote: > > The following changes since commit a000b7950da938d2df37ec5e081cd0680e6e4bbe: ... > Trübenbach, Ralf (1): > powerpc/85xx: Fix Wrong PCIe 3 virtual address on corenet_ds platforms It appears you are changing the commit messages without notice? The posted subject was: QorIQ corenet_ds.h: Wrong PCIe 3 virtual address Please don't - this makes it very difficult to match your commits to postings on the ML. > 51 files changed, 1252 insertions(+), 128 deletions(-) Applied. Best regards, Wolfgang Denk
On Apr 30, 2011, at 4:03 PM, Wolfgang Denk wrote: > Dear Kumar Gala, > > In message <alpine.LFD.2.00.1104291544410.28705@right.am.freescale.net> you wrote: >> >> The following changes since commit a000b7950da938d2df37ec5e081cd0680e6e4bbe: > ... >> Trübenbach, Ralf (1): >> powerpc/85xx: Fix Wrong PCIe 3 virtual address on corenet_ds platforms > > It appears you are changing the commit messages without notice? > > The posted subject was: > > QorIQ corenet_ds.h: Wrong PCIe 3 virtual address > > Please don't - this makes it very difficult to match your commits to > postings on the ML. > >> 51 files changed, 1252 insertions(+), 128 deletions(-) > > Applied. > > Best regards, > > Wolfgang Denk I thought that was less of an issue because of our use of patchworks. - k
On Mon, May 2, 2011 at 10:00 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
> I thought that was less of an issue because of our use of patchworks.
How? Patchwork uses the same subject line as the email. There's
still the problem of trying to correlate the actual commit to the
entry in patchwork.
On the other hand, I don't know of any good way to correct a patch's
subject line without having the patch re-submitted to the mailing
list.
Dear Tabi Timur-B04825, In message <BANLkTimz0ifsCmF9oo-Q_9Sv9wC0rQtMQQ@mail.gmail.com> you wrote: > > How? Patchwork uses the same subject line as the email. There's > still the problem of trying to correlate the actual commit to the > entry in patchwork. > > On the other hand, I don't know of any good way to correct a patch's > subject line without having the patch re-submitted to the mailing > list. It's possible to match a patch based on it's content. For example, you can use something like HASH=$(/home/wd/bin/pwparser.py --hash <$MBOX) pwclient apply -h $HASH pwclient update -s 'Accepted' -h $HASH [error checking omitted here] to apply and update the status of a patch in PW. So you can of course find out which patch it was based on the hash, which depends on the content, not the subject. But this is way too expensive and time consuming for regular work. Best regards, Wolfgang Denk
Dear Kumar Gala, In message <9BC90F9C-896B-47E9-B445-2692AAD1FB30@kernel.crashing.org> you wrote: > > > It appears you are changing the commit messages without notice? > > > > The posted subject was: > > > > QorIQ corenet_ds.h: Wrong PCIe 3 virtual address > > > > Please don't - this makes it very difficult to match your commits to > > postings on the ML. ... > I thought that was less of an issue because of our use of patchworks. Think that thought to an end, please. It is counterproductive. Best regards, Wolfgang Denk