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

Re: Verilog/ASIC development support is insufficient in git , help!

From
JLJustin Leung <jleung@redback.com>
Date
May 12, 2008, 18:45 UTC
Message-ID
<4828904B.6080708@redback.com>
In-Reply-To
<F975216F-9B61-41FF-A7FE-3D7EF09D137B@sb.org>
Thanks Kevin,
   I think i better give svn another serious look . 

but then, my impression from the rest of the people is that p4 and svn are not the ultimate tools for hardware development either .

I guess we just do not have the perfect tool for asic dev yet .
 Justin
Kevin Ballard wrote:
Show 12 quoted lines
> But they come at an expense - no more linear revision numbers, more 
> complex commands, etc. You can't have it both ways.
>
> You could always use a main SVN repo and then use git-svn to maintain 
> your own private git repos, do all the code syncing you want there, 
> and then push it back to SVN when you want to send it back to the main 
> build stream. If you go this route, be careful to maintain a linear 
> history on the branch that tracks the SVN repo, as SVN cannot handle 
> merges the way git can. You'll want to either do rebasing or squashed 
> merges (to avoid multiple parents).
>
> -Kevin Ballard
Previous: Kevin BallardNext: Dana How
Message 5 of 11 in “Verilog/ASIC development support is insufficient in git , help!”
  1. Justin LeungMay 11, 2008
  2. Kevin BallardMay 11, 2008
  3. Justin LeungMay 11, 2008
  4. Kevin BallardMay 11, 2008
  5. Justin LeungMay 12, 2008
  6. Dana HowMay 12, 2008
  7. Justin LeungMay 12, 2008
  8. Christian MICHONMay 11, 2008
  9. Justin LeungMay 12, 2008
  10. Jakub NarebskiMay 11, 2008
  11. Daniel BarkalowMay 12, 2008

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.