Re: Directing patches to linux-tegra-2.6.36 vs. Tegra's for-next?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 21, 2010 at 3:21 PM, Stephen Warren <swarren@xxxxxxxxxx> wrote:
> When submitting patches to the linux-tegra mailing list, how should I
> indicate if that patch is intended to fix something in linux-tegra-2.6.36,
> android-tegra-2.6.36, or be submitted into Tegra's for-next?
>
> I suppose I could just put something into the email body, but that'd be
> indistinguishable from the git commit comment, so the committer would have
> to manually remove it. Is there a better way?
>
> Thanks.
>
> --
> nvpublic
>
>

Either send a patch stack description (usually seen as [PATCH 0/2]),
or put it after the -- in the email body, which will be ignored by git
am.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [ARM Kernel]     [Linux ARM]     [Linux ARM MSM]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux