git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pazu <pazu@pazu.com.br>
To: git@vger.kernel.org
Subject: core-git and porcelains
Date: Wed, 11 Oct 2006 11:39:08 -0300	[thread overview]
Message-ID: <egivn8$5mf$1@sea.gmane.org> (raw)

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?

-- Marcus

             reply	other threads:[~2006-10-11 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 14:39 Pazu [this message]
2006-10-11 15:08 ` core-git and porcelains Shawn Pearce
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='egivn8$5mf$1@sea.gmane.org' \
    --to=pazu@pazu.com.br \
    --cc=git@vger.kernel.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).