From: Justin Leung <jleung@redback.com>
To: Kevin Ballard <kevin@sb.org>
Cc: git@vger.kernel.org, justin0927@hotmail.com
Subject: Re: Verilog/ASIC development support is insufficient in git , help!
Date: Mon, 12 May 2008 11:45:31 -0700 [thread overview]
Message-ID: <4828904B.6080708@redback.com> (raw)
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:
> 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
next prev parent reply other threads:[~2008-05-12 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EB66C79C87CF49E59CB39EA4C286AE05@justinuTop>
2008-05-11 5:08 ` Verilog/ASIC development support is insufficient in git , help! Justin Leung
2008-05-11 5:21 ` Kevin Ballard
2008-05-11 5:29 ` Justin Leung
2008-05-11 5:33 ` Kevin Ballard
2008-05-12 18:45 ` Justin Leung [this message]
2008-05-12 5:57 ` Dana How
2008-05-12 19:02 ` Justin Leung
2008-05-11 9:21 ` Christian MICHON
2008-05-12 18:51 ` Justin Leung
2008-05-11 9:23 ` Jakub Narebski
2008-05-12 23:09 ` Daniel Barkalow
[not found] <20080511172549.28205.qmail@science.horizon.com>
2008-05-12 18:54 ` Justin Leung
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=4828904B.6080708@redback.com \
--to=jleung@redback.com \
--cc=git@vger.kernel.org \
--cc=justin0927@hotmail.com \
--cc=kevin@sb.org \
/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;
as well as URLs for NNTP newsgroup(s).