llvm dev - Apr 2019 - How can I submit two patches for review

Hi All,

I have made changes in clang side and llvm side for one ticket. How can I submit
two patches(clang patch and llvm patch) for review ?

Can I submit two patches in single revision or have to submit separate and tag
them both?

Could any one please give your suggestions.

Thanks & Regards,
Ramakota.




IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190404/290bcc32/attachment.html>

Hi Ramakota,

If you are working from a git clone of the "monorepo" then you should
be able to do a git-diff from the top level directory (parent of the llvm and
clang directories) and post that as a single patch.
If you are working from an SVN checkout, it's probably better to generate
two diffs and post them separately. I'd post the LLVM part first, and then
when you post the Clang part, point to the LLVM part.

--paulr

From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Ramakota
Reddy via llvm-dev
Sent: Thursday, April 04, 2019 6:28 AM
To: llvm-dev at lists.llvm.org
Subject: [llvm-dev] How can I submit two patches for review

Hi All,

I have made changes in clang side and llvm side for one ticket. How can I submit
two patches(clang patch and llvm patch) for review ?

Can I submit two patches in single revision or have to submit separate and tag
them both?

Could any one please give your suggestions.

Thanks & Regards,
Ramakota.




IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190404/166ee5bd/attachment.html>

Thanks for your information paul.

From: paul.robinson at sony.com <paul.robinson at sony.com>
Sent: Thursday, April 4, 2019 4:19 PM
To: Ramakota Reddy <Ramakota.Reddy at arm.com>
Cc: llvm-dev at lists.llvm.org
Subject: RE: How can I submit two patches for review

Hi Ramakota,

If you are working from a git clone of the "monorepo" then you should
be able to do a git-diff from the top level directory (parent of the llvm and
clang directories) and post that as a single patch.
If you are working from an SVN checkout, it's probably better to generate
two diffs and post them separately. I'd post the LLVM part first, and then
when you post the Clang part, point to the LLVM part.

--paulr

From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Ramakota
Reddy via llvm-dev
Sent: Thursday, April 04, 2019 6:28 AM
To: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Subject: [llvm-dev] How can I submit two patches for review

Hi All,

I have made changes in clang side and llvm side for one ticket. How can I submit
two patches(clang patch and llvm patch) for review ?

Can I submit two patches in single revision or have to submit separate and tag
them both?

Could any one please give your suggestions.

Thanks & Regards,
Ramakota.




IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190404/bb110cf2/attachment.html>