nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] [PATCH 03/17] add support for gnulib


From: Mike Frysinger
Subject: Re: [Nano-devel] [PATCH 03/17] add support for gnulib
Date: Tue, 7 Mar 2017 18:32:45 -0500

On 02 Mar 2017 11:03, Benno Schulenberg wrote:
> When running ./autogen.sh, I get this:
> 
> Already up-to-date.
> fatal: reference is not a tree: 4084b3a1094372b960ce4a97634e08f4538c8bdd
> 
> When I cd to the gnulib/ subdir and do 'git log', I get just this:
> 
> commit a59926b805d7708b2ecc5fdcd7743810e963e859
> Author: Bruno Haible <address@hidden>
> Date:   Sun Feb 26 18:05:12 2017 +0100
> 
>     nproc: Refactor large function.
>     
>     * lib/nproc.c (num_processors_ignoring_omp): New function, extracted
>     from num_processors.
>     (num_processors): In this function, only deal with OMP.
> 
> Using --depth=5 doesn't help.  But using no depth at all
> takes far too long: 149584 deltas... wait... wait... wait...
> 
> Using --depth=222 works and does not take /too/ long, but...
> how to know how many revisions are enough?
> 
> Trying with --shallow-since=2.months.ago gives:
> 
> fatal: Server does not support --shallow-since
> 
> We would need a --shallow-from=<hash>, but if it
> existed the server probably would not support it either.

hrm, good point.  i don't think there's a way to use a pinned
hash and a --depth option at the same time.  once upstream adds
300 more commits, this script will break again.

we can drop --depth, or we can drop the hash.  most gnu projects
simply fetch the latest version all the time and use that.
-mike

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]