From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Pazu <pazu@pazu.com.br>
Cc: git@vger.kernel.org
Subject: Re: core-git and porcelains
Date: Wed, 11 Oct 2006 20:08:46 +0200 [thread overview]
Message-ID: <200610112008.46873.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <egivn8$5mf$1@sea.gmane.org>
onsdag 11 oktober 2006 16:39 skrev Pazu:
[...]
> 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.
I work against a CVS repo in the way you want to use SVN and I find StGIT
to be a perfect fit for my needs. StGIT's doesn't replace GIT's command so I
use StGIT for it's patch management and the standard git commands for the
rest. I can't see that working agains SVN should be any different, except
the git-svn* vs git-cvs commands.
The GIT commands aren't that hard to understand. The difficulty is to know
which commands to use. I use these commands
stg init, new, add, remove push, pop, refresh, status, pull, goto, diff (and a
new command float that I wrote which simplified some pop-push sequences)
git log push, diff
In addition I use qgit for browsing when git log isn't comfortable enough and
occasionally the standard patch command.
-- robin
prev parent reply other threads:[~2006-10-11 18: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
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 [this message]
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=200610112008.46873.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--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 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).