git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Roger Garvin <yoyodyn@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Suggested Workflow Question
Date: Wed, 18 Mar 2009 14:52:53 +0100	[thread overview]
Message-ID: <200903181452.53497.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <loom.20090318T125717-946@post.gmane.org>

onsdag 18 mars 2009 14:00:51 skrev Roger Garvin <yoyodyn@gmail.com>:
> Martin Langhoff <martin.langhoff <at> gmail.com> writes:
> 
> > We've done a ton of that. Even better than emailing is that you can
> > have a repo on a usb stick/disk.
> > 
> 
> That would be great except that most of our customers do not technically allow
> us to plug USB drives into any of their computers.  It's a rather silly rule
> actually but the drives could be confiscated. 
> 
> Thank you for the links to the other thread.  I will read through those today.
> I am hoping that this is simpler in practice than it looks on paper, cause what
> I see on paper is a fully connected graph of all our employees with all our
> customers multiple source locations and with our office server.  It seems like
> it could get out of control for tracking where changes might be (who is holding
> them)

Don't forget the option of mailing bundles (man git-bundle). Those will give the effect of push/fetch via e-mail. I.e. the exact same commit SHA's get replicated, That may be relevant for the branches that contain your released/official test code.

-- robin

  reply	other threads:[~2009-03-18 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 17:51 Suggested Workflow Question Roger Garvin
2009-03-18  1:27 ` Marcel M. Cary
2009-03-18  3:54   ` Marcel M. Cary
2009-03-18  4:41   ` Martin Langhoff
2009-03-18 13:00     ` Roger Garvin
2009-03-18 13:52       ` Robin Rosenberg [this message]
2009-04-17 21:11         ` Roger Garvin

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=200903181452.53497.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=yoyodyn@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).