Re: git guidance

From: Al Boldi <a1426z@gawab.com>
Date: Nov 28, 2007, 17:14 UTC
Message-ID: <200711282014.27299.a1426z@gawab.com>
In-Reply-To: <Pine.LNX.4.64.0711281545170.27959@racer.site>

Johannes Schindelin wrote:

> Hi,

Hi!

git@vger sometimes bounces, so let's leave lkml as backup.

Show 16 quoted lines

> On Wed, 28 Nov 2007, Rogan Dawes wrote:
> > Al Boldi wrote:
> > > Willy Tarreau wrote:
> > > > It should not turn into an endless thread led by people who want to
> > > > redefine GIT's roadmap, but experience sharing helps a lot with GIT.
> > >
> > > Well, now that you mentioned it, if there is one thing I dislike, it's
> > > for version control to start mutilating your sources.  Version Control
> > > should be completely transparent.  GIT isn't.
> >
> > Care to explain? Git is quite happy handling arbitrary binary content,
> > so I find it difficult to believe that it is changing your source code
> > in strange ways.
>
> It is nice of you to ask him to explain: Unless this handwaving claim is
> substantiated, it is quite hard to argue with.

Sure, the problem with GIT is that it stores the sources inside a backend container that is only accessible via GIT; iow, you can't retrieve your sources directly / transparently.

One way to achieve transparency could be to allow mounting GIT on a dir-mount point. And just use that dir normally, while GIT manages all the rest in the background.

Thanks!

-- Al