From: No Wayman <iarchivedmywholelife@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Support building Org from shallow clone [9.6.1 (release_9.6.1-137-gecb62e @ /home/n/.emacs.d/elpaca/builds/org/)]
Date: Thu, 19 Jan 2023 20:38:32 -0500 [thread overview]
Message-ID: <87wn5it214.fsf@gmail.com> (raw)
In-Reply-To: <87bkmu4vqg.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> No Wayman <iarchivedmywholelife@gmail.com> writes:
>
>> No Wayman <iarchivedmywholelife@gmail.com> writes:
>>
>>> The attached patch should take care of that.
>
> Thanks!
>
> I played a bit more with the patch and noticed that remote tag
> lookup is
> not performed prior to _any_ make command.
> For example, there is a noticeable delay on my network when
> running
> something as simple as make clean.
>
> Maybe it would be better to download the tags instead of running
> ls-remote every time? I also imagine that ls-remote might pull
> newer
> tags compared to the actual clone.
>
> An alternative could be postponing git ls-remote call to when
> the actual
> targets using GITVERSION are being called.
Feel free to take this the patch as a base to do whatever you
please with it.
I've run out of free time to iterate on it.
next prev parent reply other threads:[~2023-01-20 1:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 20:01 [PATCH] Support building Org from shallow clone [9.6.1 (release_9.6.1-137-gecb62e @ /home/n/.emacs.d/elpaca/builds/org/)] No Wayman
2023-01-15 20:55 ` No Wayman
2023-01-16 13:38 ` Ihor Radchenko
2023-01-16 19:11 ` No Wayman
2023-01-17 10:38 ` Ihor Radchenko
2023-01-18 23:11 ` No Wayman
2023-01-18 23:12 ` No Wayman
2023-01-19 11:19 ` Ihor Radchenko
2023-01-20 1:38 ` No Wayman [this message]
2023-01-20 12:44 ` Ihor Radchenko
2023-01-20 14:50 ` Max Nikulin
2023-02-10 13:21 ` Ihor Radchenko
2023-01-20 17:34 ` No Wayman
2023-01-21 9:36 ` Ihor Radchenko
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn5it214.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).