git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guilhem Bonnefille" <guilhem.bonnefille@gmail.com>
To: "Git List" <git@vger.kernel.org>
Subject: Tips for different workflows/use cases
Date: Sun, 3 Feb 2008 16:08:07 +0100	[thread overview]
Message-ID: <8b65902a0802030708i204d1714od850a59d9d25d0c1@mail.gmail.com> (raw)

Hi,

<my_life>
Up to recently, I used Git as a frontend to many SVN repo. The
workflow is simple: a central SVN and a single "client" desktop.
Now, I started to use Git at office. So I "discover" new problems and
my actual experience is not enougth.
</my_life>

Actually, I discovered two(/three) use cases for which I'm looking the
best (recommended) workflows. My idea is to identify the best
practices to avoid (as possible) complex situations.
1- The same developer uses two repo on two network connected computers.
For any reason, a developer has to work on two computers for the same
project. He sometimes hack on both computers. He uses two git
repositories to keep it work in sync. Note: the two computers are
connected, and the developer can pull/push via ssh.
So, what is the best practices:
- should he decide to push/pull every time from the same repo or
should he only use the "pull" command on each repo (and never push)
- should he decide to create a third repo and use it as central repo.

2- It's a variation of the previous one. Now, one of the two computers
is a laptop. Is there any recommended practices to work with laptop?

3- Now, the two computer are not connected via network. Two possible
solutions to sync our both computers: USB disk and e-mail.
Any recommendation in this context?


I think that such recommendations must be shared on the wiki, for
example on GitWorkflows or GitFaq pages.
-- 
Guilhem BONNEFILLE
-=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/

             reply	other threads:[~2008-02-03 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 15:08 Guilhem Bonnefille [this message]
2008-02-03 21:49 ` Tips for different workflows/use cases Dmitry Potapov

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=8b65902a0802030708i204d1714od850a59d9d25d0c1@mail.gmail.com \
    --to=guilhem.bonnefille@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).