git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Sheedy <kevinsheedy@gmail.com>
To: git@vger.kernel.org
Subject: Push to all repositories
Date: Wed, 8 Dec 2010 09:39:43 -0800 (PST)	[thread overview]
Message-ID: <1291829983410-5816069.post@n2.nabble.com> (raw)


Will git let me push my changes to every member of the team?

I find a big problem with CVS & SVN is that I have to explicitly update my
code in order to keep in sync. This is a real pain-point as I often have to
do it several times a day and it can be very slow. We still regularly get
problems caused by developers being out of sync. Most people become
reluctant to do an update at all as they fear it will cause errors.

Clearcase has a great solution to this, "dynamic views". Whenever I check in
some code, the whole team magically get's my changes straight away.
Normally, they don't even notice, they're just forced to stay in sync. This
drastically reduces the number of 'code conflicts' where people make changes
to 'stale' files. This enforces the practise of "catching errors early". It
also keeps developers "honest" as they have to keep the quality of their
checkins high lest they get shouted at by the rest of the team.

Will git let a team stay in sync without everyone having to do manual
updates?
Basically, I want every developer to be able to push their code to the whole
team.
-- 
View this message in context: http://git.661346.n2.nabble.com/Push-to-all-repositories-tp5816069p5816069.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2010-12-08 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:39 Kevin Sheedy [this message]
2010-12-08 18:00 ` Push to all repositories Jonathan Nieder
2010-12-08 22:59   ` Kevin Sheedy
2010-12-09 12:36     ` Kevin Sheedy
2010-12-09 12:47       ` Nguyen Thai Ngoc Duy
2010-12-09 13:36       ` Martin von Zweigbergk
2010-12-09 19:52         ` Jonathan Nieder
2011-01-02  9:54           ` Enrico Weigelt
2010-12-12 15:09 ` Enrico Weigelt

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=1291829983410-5816069.post@n2.nabble.com \
    --to=kevinsheedy@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).