From: Martin Langhoff <martin.langhoff@gmail.com>
To: James Pickens <jepicken@gmail.com>
Cc: Greg Hauptmann <greg.hauptmann.ruby@gmail.com>, git@vger.kernel.org
Subject: Re: do you recommend "git" (over svn) for a 1-person team???
Date: Thu, 29 Jan 2009 15:28:09 +1300 [thread overview]
Message-ID: <46a038f90901281828t16ace3bdocc897eb5235d7c30@mail.gmail.com> (raw)
In-Reply-To: <885649360901281815q42199468v8658d864386efe2d@mail.gmail.com>
On Thu, Jan 29, 2009 at 3:15 PM, James Pickens <jepicken@gmail.com> wrote:
> Greg Hauptmann <greg.hauptmann.ruby@gmail.com> wrote:
>> Do you recommend "git" (over svn) for a 1-person team???
>
> Yes, emphatically. I do it myself all the time.
+1!
- offline work on your laptop
- "git stash"
- keep various branches (experimental, feature, stable...), with
untold flexibility for cherrypicking, merges, etc
- bisect!
- visualise things with gitk
- search with gitk for specific bits of code, changes (pickaxe), etc
once you start... it's a bit addictive...
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-01-29 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d30068860901281718x363348caya2dc94e798cc8091@mail.gmail.com>
2009-01-29 1:25 ` do you recommend "git" (over svn) for a 1-person team??? Greg Hauptmann
2009-01-29 1:38 ` Sverre Rabbelier
2009-01-29 2:09 ` Ted Pavlic
2009-01-29 2:15 ` James Pickens
2009-01-29 2:28 ` Martin Langhoff [this message]
2009-01-29 2:46 ` Greg Hauptmann
2009-01-29 3:31 ` Ted Pavlic
2009-01-29 4:05 ` Jeff King
2009-01-29 3:27 ` Ted Pavlic
2009-01-29 2:21 ` Garry Dolley
2009-01-29 2:57 ` david
2009-01-30 12:46 ` Jakub Narebski
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=46a038f90901281828t16ace3bdocc897eb5235d7c30@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=greg.hauptmann.ruby@gmail.com \
--cc=jepicken@gmail.com \
/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).