From mboxrd@z Thu Jan 1 00:00:00 1970 From: david@lang.hm Subject: Re: metastore Date: Sat, 15 Sep 2007 18:49:29 -0700 (PDT) Message-ID: References: <20070915132632.GA31610@piper.oerlikon.madduck.net> <20070915145437.GA12875@piper.oerlikon.madduck.net> <86veaby050.fsf@blue.stonehenge.com> <86r6kzxvnm.fsf@blue.stonehenge.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Grzegorz Kulewski , martin f krafft , git@vger.kernel.org, Johannes Schindelin , "Thomas Harning Jr." , Francis Moreau , Nicolas Vilz , David =?iso-8859-1?Q?H=E4rdeman?= To: "Randal L. Schwartz" X-From: git-owner@vger.kernel.org Sun Sep 16 03:50:20 2007 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1IWjH6-0004Qc-86 for gcvg-git-2@gmane.org; Sun, 16 Sep 2007 03:50:16 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754060AbXIPBuE (ORCPT ); Sat, 15 Sep 2007 21:50:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754031AbXIPBuE (ORCPT ); Sat, 15 Sep 2007 21:50:04 -0400 Received: from dsl081-033-126.lax1.dsl.speakeasy.net ([64.81.33.126]:56583 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754045AbXIPBuB (ORCPT ); Sat, 15 Sep 2007 21:50:01 -0400 Received: from asgard (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id l8G1nTck021495; Sat, 15 Sep 2007 18:49:29 -0700 X-X-Sender: dlang@asgard.lang.hm In-Reply-To: <86r6kzxvnm.fsf@blue.stonehenge.com> Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Sat, 15 Sep 2007, Randal L. Schwartz wrote: >>>>>> "david" == david writes: > >>> Why does everyone keep wanting "work dir == live dir". Ugh! The work dir is >>> the *source*... it gets *copied* into your live dir *somehow*. And *that* is >>> where the meta information needs to be. In that "somehow". > > david> the problem is that at checkin you need to do the reverse process. the > david> other tools that you use on the system work on the live dir, not the > david> 'work dir', so it's only a 'work dir' in that git requires it as an > david> staging step between the repository and the place where it's going to > david> be used. > > Eh? Are we still talking about a "website", or "/etc"? I'm talking about the > website case. I don't do *anything* to the live site. When I want to add a > file, I add it to my dev repo, possibly modifying my Makefile, and then spit > it out on my staging server. (You *do* have one of those, right?) Once I > know it's good, I push it to the live repo, and then "go live" with it. I > *never* work on the files that are the result of "make install". even when working on a website it can be relavent. yes, when you are developing html you want to do it on a test server , move it to staging, and then move to production. but it's also not uncommon to have web based tools that allow other people to make some changes as well (for example, a bank's website is mostly maintained by their web development company, but the bank administraters want the ability to change rate information instantly). sometimes this is implemented by writing the info to a database and then querying that database for every hit, but a far more efficiant way is to store that data in a file on the webserver, which can include modifying pages directly. but yes, I was mostly thinking of /etc instead of the webserver when I wrote that. David Lang