git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Suggested Workflow Question

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Mar 18, 2009, 04:41 UTC
Message-ID
<46a038f90903172141o7b272c17v2c485bb66b529fe8@mail.gmail.com>
In-Reply-To
<49C04DFC.10201@earth.care2.com>
On Wed, Mar 18, 2009 at 2:27 PM, Marcel M. Cary <marcel@earth.care2.com> wrote:
> * emailing patches when direct connections are not possible
> * test and dev branches for each customer

We've done a ton of that. Even better than emailing is that you can have a repo on a usb stick/disk.

 - At the office, update it from the 'office' repository.
 - At the client site, pull updates from the usb stick, and push any
code developed at teh client side to the stick
 - Back at the office, push to the office repo
cheers,
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
Previous: Marcel M. CaryNext: Roger Garvin
Message 4 of 7 in “Suggested Workflow Question”
  1. Roger GarvinMar 17, 2009
  2. Marcel M. CaryMar 18, 2009
  3. Marcel M. CaryMar 18, 2009
  4. Martin LanghoffMar 18, 2009
  5. Roger GarvinMar 18, 2009
  6. Robin RosenbergMar 18, 2009
  7. Roger GarvinApr 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.