All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Pazu <pazu@pazu.com.br>
Cc: git@vger.kernel.org
Subject: Re: core-git and porcelains
Date: Wed, 11 Oct 2006 11:08:42 -0400	[thread overview]
Message-ID: <20061011150842.GA31298@spearce.org> (raw)
In-Reply-To: <egivn8$5mf$1@sea.gmane.org>

Pazu <pazu@pazu.com.br> wrote:
> I'm a newcomer to git, and for the last few days, I've been struggling 
> to learn how to better use git in my day to day. One particular thing 
> that has been puzzling me is how much git is self-sufficient, and how 
> much I should depend on porcelains.
> 
> Apparently, I'm not alone in this: 
> http://thread.gmane.org/gmane.comp.version-control.git/6194/focus=6194
> 
> The above post was made about three months ago; where things stand now? 
> Do you feel that git-core should suffice for most developers, or should 
> I really look into something like Cogito?
> 
> Depending on the project, my git usage would fit one of two profiles. I 
> run some standalone projects, where I'm the sole developer. I was 
> looking into using cogito for this scenario, but one thing that baffled 
> me is how git-core and cogito use different branch representations.
> 
> For the larger part of my day, however, I'm looking into using git as a 
> personal tool in a very large corporate project; This project is 
> currently controlled using subversion, and my idea is to use git as a 
> 'staging' system, where I work (possibly offline) before pushing changes 
> to the upstream (remote, slow as hell) subversion repository. Here, 
> git-svn seems to be my best friend.
> 
> Any advice to this poor newbie?

I would just stick with core Git.  I haven't used Cogito in almost
a year so I can't say what I'm missing there, but core Git works
very well for all of my needs.  I use it in a lot of different
projects, some which require git-svn, others which require some
bastard git-svn-workalike for non-SVN systems, and others which
are just Git projects and don't have to cooperate with others.

Git has come a long way in terms of user interface.  It still has a
few rough edges but I think that there are less rough edges on core
Git's command line user interface than there are on the Subversion
command line client or the CVS command line client.

-- 
Shawn.

  reply	other threads:[~2006-10-11 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 14:39 core-git and porcelains Pazu
2006-10-11 15:08 ` Shawn Pearce [this message]
2006-10-11 16:45   ` Pazu
2006-10-11 16:54     ` Shawn Pearce
2006-10-11 17:13       ` Pazu
2006-10-11 17:01   ` Seth Falcon
2006-10-11 18:08 ` Robin Rosenberg

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=20061011150842.GA31298@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=pazu@pazu.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.