From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@kernel.org>
Cc: Prasad Joshi <prasadjoshi124@gmail.com>,
kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com,
oswaldo.cadenas@gmail.com
Subject: Re: [PATCH 3/4] Provides the basic Gitish framework
Date: Fri, 8 Apr 2011 08:10:39 +0200 [thread overview]
Message-ID: <20110408061039.GC902@elte.hu> (raw)
In-Reply-To: <1302241489.32207.50.camel@jaguar>
* Pekka Enberg <penberg@kernel.org> wrote:
> On Thu, 2011-04-07 at 23:33 +0100, Prasad Joshi wrote:
> > On Thu, Apr 7, 2011 at 9:14 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > * Prasad Joshi <prasadjoshi124@gmail.com> wrote:
> > >
> > >> - kvm-cmd.h: Adds a new structure cmd_struct to create a table of commands
> > >> and callback function.
> > >>
> > >> - kvm-cmd.c: implements two main functions for command processing.
> > >> kvm_get_command(): searches table for specific command.
> > >> handle_command(): invokes the callback function for a given command.
> > >>
> > >> - kvm-help.[ch] Implements the kvm help command.
> > >
> > > Please credit the people/projects from where you took these bits.
> >
> > Oh yes!
> > struct cmd_struct and list_common_cmds_help() is copied from perf.
>
> Please just add that to the changelog.
Yeah - and perf took it from Git :-)
The way we credited the Git project in perf was this commit:
1b173f77dd0d: perf_counter tools: Add CREDITS file for Git contributors
basically a CREDITS file for Git library contributors. If you expect to take
more bits, such as the help system (look at tools/perf/Documentation/) and
other bits, the easiest solution would be for you to take the CREDITS file and
name it CREDITS-lib or so.
This also serves as a way to grandfather in other history (and copyrights), the
exact upstream Git sha1 is mentioned. The Git project is GPLv2 as well like the
kernel and like tools/perf/, so this works out well and you do not have to
re-credit again and again so precisely, as you take more bits of Git's library
code.
Thanks,
Ingo
next prev parent reply other threads:[~2011-04-08 6:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 19:47 [PATCH 1/4] Generating list of common kvm tool commands Prasad Joshi
2011-04-07 19:47 ` [PATCH 2/4] Mostly the copied code from perf for argument processing Prasad Joshi
2011-04-07 20:17 ` David Ahern
2011-04-08 5:43 ` Pekka Enberg
2011-04-08 6:04 ` Ingo Molnar
2011-04-07 19:47 ` [PATCH 3/4] Provides the basic Gitish framework Prasad Joshi
2011-04-07 20:14 ` Ingo Molnar
2011-04-07 22:33 ` Prasad Joshi
2011-04-08 5:44 ` Pekka Enberg
2011-04-08 6:10 ` Ingo Molnar [this message]
2011-04-07 19:47 ` [PATCH 4/4] Using the Gitish freamwork to run the virtual machine Prasad Joshi
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=20110408061039.GC902@elte.hu \
--to=mingo@elte.hu \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=oswaldo.cadenas@gmail.com \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@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