From: Duy Nguyen <pclouds@gmail.com>
Date: Thu, 05 Mar 2015 00:26:43 GMT
Subject: Re: [RFH] GSoC 2015 application
Message-ID: <CACsJy8BcL3=uYa6=zA9UfV5A9sYqhcrJte40y03sfCcsCkKdhA@mail.gmail.com>
In-Reply-To: <CAGZ79kaNZsBP19gLvsrDx6RLyQ7QhmbKAgSDcXg71Uwcvf9tNQ@mail.gmail.com>

On Thu, Mar 5, 2015 at 6:55 AM, Stefan Beller <sbeller@google.com> wrote:
> On Wed, Mar 4, 2015 at 2:05 PM, Philip Oakley <philipoakley@iee.org> wrote:
>
>> A possible idea is to add a date based variant of shallow clone :
>>
>>  'git clone --date <when> ...'
>>
>> in the same vein as the existing depth (shallow) clone.
>
> As food for thought:
> Maybe broaden this further up to the git-ish way of describing refs, so
>
>     git clone --since 2.weeks.ago <url>
>     git clone --since v2.10 <url>
>     git clone --since c0ffee^^ <url>
>
> would all equally work?

Yes, and we could generalize it further: add shallow-rev-list
capability and send "shallow-rev-list <rev-list options and _some_
rev>" line to define shallow boundary. The protocol change would be
simple enough. The hard part is select a safe subset of rev-list
options that can be used in this mode and reject the rest.

> I am not sure if that is feasible though, but it would come in handy. (E.g.
> you are an end user and want to bisect down a bug which you notice in the
> new version X but not in old version Y, so you start on getting the sources,
> compiling, bisecting)
-- 
Duy