linux-kernel - Re: why are some of my patches being credited to other "authors"?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.63.0612091327540.24913@gockel.physik3.uni-rostock.de>
Date:	Sat, 9 Dec 2006 13:39:33 +0100 (CET)
From:	Tim Schmielau <tim@...sik3.uni-rostock.de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?

> but it still leaves an open issue -- once one submits a patch, is there 
> *any* official feedback that one can look for to see if it's been 
> accepted/rejected/dropped on the floor/whatever?

You can regularely pull Linus' tree (or the tree of the maintainer you 
sent your patch) and see whether your patches still apply cleanly. 
Whenever they cause a reject, they need your attention: either they were 
applied, or they got out of date because something else changed.
(akpm also sends out automatic notification emails for patches in the -mm 
tree based on a similar method.)

> but given that i'm trying to follow the kernel guidelines and keep
> each submission as a logically-related chunk, in many cases, i have to
> wait for one patch to be applied before i can submit the next one.
> and, at the moment, there's no way of knowing what's going on.

Well, you can send out a patch series:
  [patch 01/02] Prepare foo for blah
  [patch 02/02] Apply blah to foo
Ideally you would finish the patch description for patch 02 with something 
like

---
This patch depends on [patch 01/02] Prepare foo for blah

But usually people will assume they have to apply the patches in order 
even without you explicitly telling them.
Unless you are keen on particular feedback about patch 01 before doing 
much work on patch 02, this should work out well.

Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/