[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1D40FF54-64FD-4507-8E5D-02A01F2DD8EB@vicaya.com>
Date: Fri, 7 Dec 2007 14:07:29 -0800
From: Luke Lu <git@...aya.com>
To: Valdis.Kletnieks@...edu
Cc: Al Boldi <a1426z@...ab.com>, Jakub Narebski <jnareb@...il.com>,
Andreas Ericsson <ae@....se>,
Johannes Schindelin <Johannes.Schindelin@....de>,
Phillip Susi <psusi@....rr.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jing Xue <jingxue@...izenstudio.com>,
linux-kernel@...r.kernel.org, git@...r.kernel.org
Subject: Re: git guidance
On Dec 7, 2007, at 11:36 AM, Valdis.Kletnieks@...edu wrote:
> On Fri, 07 Dec 2007 22:04:48 +0300, Al Boldi said:
>
>> Because WORKFLOW C is transparent, it won't affect other
>> workflows. So you
>> could still use your normal WORKFLOW B in addition to WORKFLOW C,
>> gaining an
>> additional level of version control detail at no extra cost other
>> than the
>> git-engine scratch repository overhead.
>>
>> BTW, is git efficient enough to handle WORKFLOW C?
>
> Imagine the number of commits a 'make clean; make' will do in a
> kernel tree, as
> it commits all those .o files... :)
My guess is that Al is not really a developer (product management/
marketing?), what he has in mind is probably not an SCM but a backup
system a la Mac's time machine or Netapp's snapshots that also
support disconnected commits. I think that git could be a suitable
engine for such systems, after a few tweaks to avoid compressing
already compressed blobs like jpeg, mp3 and mpeg etc.
__Luke
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists