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: Sat, 10 May 2008 22:29:51 -0700 [thread overview]
Message-ID: <83EE186A7AF140179C6C73B367471EC7@justinuTop> (raw)
In-Reply-To: <B03D1DC3-7088-41AF-BB8B-9A696E7C5B8E@sb.org>
Hi Kevin,
The ability of inter-user (designer-verifier) code sync'ing without letting
the incomplete or incompatible RTL code to propagate to the main build
stream is going to facilitate the design flow and efficiency .
The ability of local revision control means that no more over writing of
design files until commit .
I think these 2 things will really buy us alot .
Justin
> Honestly, it sounds like SVN is actually a good fit here. Just because
> git is awesome for many things does not mean it is the end-all-be-all of
> version control systems. SVN still has its place as the last true
> centralized system. Given your constraints and workflow, why do you think
> git is better than SVN?
>
> -Kevin Ballard
>
> --
> Kevin Ballard
> http://kevin.sb.org
> kevin@sb.org
> http://www.tildesoft.com
>
>
>
next prev parent reply other threads:[~2008-05-11 5:30 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 [this message]
2008-05-11 5:33 ` Kevin Ballard
2008-05-12 18:45 ` Justin Leung
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=83EE186A7AF140179C6C73B367471EC7@justinuTop \
--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