On Sat, Mar 30, 2019 at 5:02 AM Joe Enzminger
wrote:
>
> Duy -
>
> Any updates on this feature request?
Nope. I've been busy with other stuff. I did have a look at the
possibility of reusing code in sha1-name.c and concluded that it's not
quite safe.
> Joe
>
> On Thu, Feb 21, 2019 at 7:06 AM Duy
Duy -
Any updates on this feature request?
Joe
On Thu, Feb 21, 2019 at 7:06 AM Duy Nguyen wrote:
>
> On Thu, Feb 21, 2019 at 1:07 AM Joe Enzminger
> wrote:
> >
> > That is correct. What you suggest is actually what I tried (using
> > sha-1 syntax). For my purposes, excluding the tag's parent
On Thu, Feb 21, 2019 at 1:07 AM Joe Enzminger
wrote:
>
> That is correct. What you suggest is actually what I tried (using
> sha-1 syntax). For my purposes, excluding the tag's parent's but
> including the tag is sufficient, but if is fairly straightforward to
> extend support to the other use c
That is correct. What you suggest is actually what I tried (using
sha-1 syntax). For my purposes, excluding the tag's parent's but
including the tag is sufficient, but if is fairly straightforward to
extend support to the other use cases I'm sure someone would find is
useful.
Joe
On Tue, Feb 1
On Wed, Feb 20, 2019 at 7:07 AM Joe Enzminger
wrote:
>
> Currently, git clone supports shallow-exclude=. The client
> will clone up to, but not including, the commit with the tag.
>
> It would be useful to have the ability to include the commit with the
> tag. The suggestion would be to add a "s
Currently, git clone supports shallow-exclude=. The client
will clone up to, but not including, the commit with the tag.
It would be useful to have the ability to include the commit with the
tag. The suggestion would be to add a "shallow-include" options to
clone to support this behavior.
I hav
6 matches
Mail list logo
