From: Andreas Krey <a.krey@gmx.de>
To: Andrew Sayers <andrew-git@pileofstuff.org>
Cc: Daniele Segato <daniele.bilug@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's the best way to make my company migrate to Git?
Date: Wed, 2 Jun 2010 07:19:07 +0200 [thread overview]
Message-ID: <20100602051907.GA19934@inner.home.ulmdo.de> (raw)
In-Reply-To: <4C0577D1.6030805@pileofstuff.org>
On Tue, 01 Jun 2010 22:12:49 +0000, Andrew Sayers wrote:
...
> I think it's also worth mentioning local/remote commits, as it's quite
> easy for people to commit and forget to push.
I found (for myself) 'gitk --all' making it lots easier to see the light
in these regards. (Missing such a thing for svn sorely.) Doing a fetch,
pressing F5 and seeing the remote branches move. Or diverge.
Andreas
next prev parent reply other threads:[~2010-06-02 5:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:55 What's the best way to make my company migrate to Git? Daniele Segato
2010-05-21 15:54 ` Jakub Narebski
2010-05-22 15:58 ` Daniele Segato
2010-05-22 16:06 ` Jakub Narebski
2010-05-22 18:26 ` Joshua Jensen
2010-05-22 10:52 ` Andrew Sayers
2010-05-22 15:52 ` Daniele Segato
2010-05-23 14:52 ` Andrew Sayers
2010-05-24 17:37 ` Daniele Segato
2010-05-23 9:12 ` Lin Mac
2010-05-23 15:06 ` Andrew Sayers
2010-05-25 7:42 ` Michael J Gruber
2010-05-31 20:04 ` Andrew Sayers
2010-06-01 6:28 ` Michael J Gruber
2010-06-01 16:00 ` Daniele Segato
2010-06-01 16:14 ` Alexander Iljin
2010-06-01 17:16 ` Daniele Segato
2010-06-01 17:45 ` Alexander Iljin
2010-06-01 16:25 ` Erik Faye-Lund
2010-06-01 16:36 ` Daniele Segato
2010-06-01 21:12 ` Andrew Sayers
2010-06-02 5:19 ` Andreas Krey [this message]
2010-06-02 7:15 ` Michael J Gruber
2010-06-05 21:27 ` Andrew Sayers
2010-06-06 8:19 ` Steven Michalske
2010-06-02 16:01 ` Sylvain Rabot
[not found] ` <AANLkTilIihNTDPZ5NIKUzsPEZ2Gpusm-10FCBVifvNuw@mail.gmail.com>
2010-05-23 22:46 ` Daniele Segato
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=20100602051907.GA19934@inner.home.ulmdo.de \
--to=a.krey@gmx.de \
--cc=andrew-git@pileofstuff.org \
--cc=daniele.bilug@gmail.com \
--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).