From: chrubis@suse.cz
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP <ltp-list@lists.sourceforge.net>, Jungsoo Son <jungsoo.son@lge.com>
Subject: Re: [LTP] Regarding LTP contribution
Date: Mon, 20 May 2013 13:37:05 +0200 [thread overview]
Message-ID: <20130520113704.GA19493@rei> (raw)
In-Reply-To: <6A7E2981-DEB3-4402-B0C8-7AE7FCD85236@gmail.com>
Hi!
> > My name is jungsoo son who is in charge of kernel development on my company.
> > I want to send my patch to upstream of Linux Test Project.
> > Could you give me some information about how to push git commit ?
>
> Hi jungsoo son!
> I recommend following up on ltp-list requesting these details. Also, these details should be updated in any documentation attached to the project (I think there's some IIRC).
There is quick howto at the end of doc/style-guide.txt but it's far from
complete (I really should get some time to review and update the docs).
Generally if you want to contribute to LTP send your patch to the LTP
malinling list for review. It will be pushed to LTP git once it passes
the review phase by one of our developers.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-05-20 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001701ce5200$6bdfcdb0$439f6910$@lge.com>
2013-05-18 11:48 ` [LTP] Regarding LTP contribution Garrett Cooper
2013-05-20 11:37 ` chrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130520113704.GA19493@rei \
--to=chrubis@suse.cz \
--cc=jungsoo.son@lge.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox