On Wed, May 4, 2011 at 10:13 AM, Robert Huttinger
<roberthuttin...@gmail.com> wrote:
> thanks for the heads up (hijacking my own thread) I cant use git because it
> is public, and I cant get boss to spring for private.

Perhaps I don't understand...  yes, git is open-source-software, but
are you saying that you're not permitted to run non-pay software at
all at work?  Or are you confusing git as an SCM versus hosted git
services like git-hub?

Git is an SCM just like CVS, SVN, or any other hundreds out there.
One of the best things about it is it can be used locally without a
server, and in fact can be used over the top of other SCMs.  Yes, it's
open source, but that doesn't make it bad.  And anyone who thinks that
using OSS is bad by definition needs a better understanding of OSS.
And for those who don't understand OSS licenses _using_ it doesn't
make the code/content you're keeping in it open source. Just the same
as using CVS or SVN doesn't open your code/content, or using Linux as
a server or desktop doesn't make your work-product on that computer
open souce, or using Windows gives MS rights to your content/code.

If you're simply concerned about opening private code to the public
via using a service such as git-hub, simply don't. Instantiate a git
repo over the directory you're working in.  Don't push it anywhere.
You get all the benefits of an SCM, but no server.  If you need to
collaborate with someone in your office, open that git repo to them
via ssh into your box, or pushing to a shared drive where both of you
have access, but is still secure as it is within your private network.
 And if your company is looking for an SCM solution for a team, by all
means look into git and utilize a shared server _on_your_network_ to
store trees that everyone needs to clone or pull from.  This would be
similar to running CVS, SVN, ClearCase, Mecurial, or whatever your
chosen SCM is.  In other-words, keep it internal.

Sorry, we've now gone off topic, and this will be my last comment on
this thread.  If you have specific questions on Git, feel free to
email me directly.

- Steve

-- 
You received this message because you are subscribed to the 
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem, 
please email "supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

Reply via email to