git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Option/Subcommand Processing Library?

From
MBMichael Bergin <michaeljbergin@gmail.com>
Date
Jul 26, 2009, 00:38 UTC
Message-ID
<D48B952D-501B-4B90-A2B7-00DF5F21D3A4@gmail.com>
In-Reply-To
<alpine.DEB.1.00.0907260117540.8306@pacific.mpi-cbg.de>

I really appreciate your help. I'm going to do this regardless of license so I'll ask about that when I have a finished project. Let me know if you have any suggestions for features, etc. Thanks again.

- Mike Bergin
On Jul 25, 2009, at 7:18 PM, Johannes Schindelin wrote:
Show 19 quoted lines
> Hi,
>
> On Sat, 25 Jul 2009, Michael Bergin wrote:
>
>> Thanks for the pointers.  I also want to create a generic library for
>> command facades like git.  For that I will probably use git.c as a  
>> guide
>> but to make it generic I would need to add/rearrange code.  GPLv2  
>> works
>> fine for my purposes.  I hope this isn't an offensive question or
>> anything but would releasing just the library under LGPL be  
>> considered?
>
> You need to ask all authors of all the code you reuse.  I, for one,  
> have
> no objections.
>
> Ciao,
> Dscho
Previous: Johannes Schindelin
Message 5 of 5 in “Git Option/Subcommand Processing Library?”
  1. Michael BerginJul 25, 2009
  2. Johannes SchindelinJul 25, 2009
  3. Michael BerginJul 25, 2009
  4. Johannes SchindelinJul 25, 2009
  5. Michael BerginJul 26, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.