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

Re: How to start well for a special git construction

From
Avery Pennarun <apenwarr@gmail.com>
Date
Mar 18, 2010, 20:48 UTC
Message-ID
<32541b131003181348j1e7d5dfamec09bed2c81916d8@mail.gmail.com>
In-Reply-To
<e8be804e1003181226y20328151s75641f4341ca12d8@mail.gmail.com>

On Thu, Mar 18, 2010 at 3:26 PM, bruno le hyaric <bruno.lehyaric@gmail.com> wrote:

> On the left hand, I use one framework : Spree ;
> on the other hand , I use Flex generation with another framework : RestfulX;
> on my third hand ^^, I want to merge both in a third directory.

I think you might have skipped past describing your problem and jumped straight to describing your solution.

Do you actually have multiple projects that you're working on, or are you the maintainer of an application that uses other people's projects? Do you want to make patches to these other subprojects (Spree and RestfulX) and distribute them upstream, or do you just want to use their upstream versions verbatim? Do you want to patch their projects and *not* distribute your patches upstream? Do you expect to update your copies of those projects frequently or rarely?

Are you planning to distribute copies of your source code, your finished product, or both? Ruby on Rails apps usually don't have anything *but* the source code, but in that case, I'm not sure why you mention Clearcase and not including the source code in release streams.

There are a lot of variables here and it's hard to give good advice unless we have a clearer understanding of what you actually want to accomplish.

Have fun,
Avery
Previous: bruno le hyaricNext: bruno le hyaric
Message 2 of 4 in “How to start well for a special git construction”
  1. bruno le hyaricMar 18, 2010
  2. Avery PennarunMar 18, 2010
  3. bruno le hyaricMar 19, 2010
  4. Avery PennarunMar 19, 2010

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.