This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] build-many-glibcs.py: Use --depth 1 in Git checkout

From: Florian Weimer <fweimer at redhat dot com>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: <libc-alpha at sourceware dot org>
Date: Fri, 28 Feb 2020 22:33:22 +0100
Subject: Re: [PATCH] build-many-glibcs.py: Use --depth 1 in Git checkout
References: <877e06udhu.fsf@oldenburg2.str.redhat.com> <alpine.DEB.2.21.2002282117410.23276@digraph.polyomino.org.uk>

* Joseph Myers:

> On Fri, 28 Feb 2020, Florian Weimer wrote:
>
>> The history is not used by build-many-glibcs.py itself.
>> --replace-sources deletes an existing source tree before switching
>> the version.
>> 
>> This works around networking and Git server performance issues to some
>> degree.
>
> I think making a shallow clone is unhelpful in practice since it's 
> routinely useful to revert to previous versions when finding where a 
> problem appeared.

Would it be too cumbersome to run git fetch --unshallow in this case,
before starting the investigation?

It really reduces checkout time, particularly if sourceware.org is under
load.

Thanks,
Florian

Follow-Ups:
- Re: [PATCH] build-many-glibcs.py: Use --depth 1 in Git checkout
  - From: Joseph Myers

References:
- [PATCH] build-many-glibcs.py: Use --depth 1 in Git checkout
  - From: Florian Weimer
- Re: [PATCH] build-many-glibcs.py: Use --depth 1 in Git checkout
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]