public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: git repositories for cygwin packaging - please test
Date: Tue, 13 Aug 2019 11:55:00 -0000	[thread overview]
Message-ID: <7fd3b0cd-0139-846c-beee-529fbecbe04c@dronecode.org.uk> (raw)
In-Reply-To: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk>

On 04/08/2019 21:08, Jon Turney wrote:
> 
> These repositories are viewable via gitweb at 
> https://cygwin.com/git-cygwin-packages/ (URL may be subject to change), 
> and should be cloneable via anonymous git/http with the URLs shown there.
> 
> Please give this a test, if possible, and report any problems here.

Thanks for the feedback.

I've made the following adjustments:

Updated the gitolite version to get a performance fix for creating a 
repository (so it's ~O(1) rather than ~O(number of repositories))

https://cygwin.com/git-cygwin-packages/ is now paginated to improve 
pageload.  This works moderately well when using the default sorting (by 
project), but unfortunately, it still needs to run thousands of git 
commands to get the information when sorting by last change or owner. 
The popular solutions to that problem seem to be "don't use gitweb" :).

Patched gitolite to permit repository names starting with '_', since we 
have a couple of those.

  parent reply	other threads:[~2019-08-13 11:55 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 20:08 Jon Turney
2019-08-05  2:03 ` Ken Brown
2019-08-08 13:47 ` Andrew Schulman via cygwin-apps
2019-08-08 14:04 ` Andrew Schulman via cygwin-apps
2019-08-08 17:09   ` Ken Brown
2019-08-09 16:12     ` Jon Turney
2019-08-09 19:12       ` Ken Brown
2019-08-13 11:55         ` Jon Turney
2019-08-09 16:00 ` Jon Turney
2019-08-09 20:58 ` Brian Inglis
2019-08-13 11:55 ` Jon Turney [this message]
2019-08-19 18:36 ` Achim Gratz
2020-05-27 22:27 ` Jon Turney
2020-05-28 11:51   ` szgyg
2020-06-04 16:01   ` Ken Brown
2020-06-04 20:33     ` Brian Inglis
2020-06-09 13:26       ` Jon Turney
2020-06-09 22:44         ` Brian Inglis
2020-08-06 20:20   ` Jon Turney
2020-08-06 21:04     ` Ken Brown
2020-08-07 19:42     ` Achim Gratz
2020-08-07 22:05       ` Ken Brown
2020-08-08  4:26         ` ASSI
2020-08-16 18:05         ` Jon Turney
2020-08-23 21:01   ` Jon Turney
2020-08-26 22:00     ` Ken Brown
2020-08-30 15:00       ` Jon Turney
2020-08-30 15:22         ` Ken Brown
2020-08-30 15:46           ` Jon Turney
2020-08-30 17:25             ` Ken Brown
2020-08-30 20:06               ` Jon Turney
2020-11-12 21:30             ` Jon Turney
2020-08-30 16:44         ` ASSI
2020-08-30 20:08           ` Jon Turney
2020-10-04 10:26           ` Achim Gratz
2020-10-25 18:10             ` Jon Turney
2021-05-09 14:39     ` Jon Turney
2021-06-22 19:52       ` Jon Turney
2021-06-23  4:22         ` Brian Inglis
2022-07-05 13:12         ` Jon Turney
2023-02-18 16:21           ` Jon Turney
2023-02-18 17:43             ` Ken Brown
2023-02-18 18:40               ` Jon Turney
2020-11-16 21:54   ` Brian Inglis
2020-11-16 22:16     ` Jon Turney
2020-11-16 22:54       ` Brian Inglis
2020-11-17 19:21     ` Achim Gratz
2020-05-29 14:40 ` Alexey Sokolov
2020-06-07 15:06   ` Hamish McIntyre-Bhatty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fd3b0cd-0139-846c-beee-529fbecbe04c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).