Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Support git worktree
Date: Wed, 22 Apr 2020 02:01:23 +0200	[thread overview]
Message-ID: <20200422000123.370ozhtb5SPrgidoS4RKZ8IASMRplCYR8PMm_LNyaUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21207@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/21207#issuecomment-617471997

Comment:
On 2020-04-21 09:34:46-0700, Juan RP <notifications@github.com> wrote:
> I like the idea, this will allow us to get rid of chroot-git as well.

I thought about get rid of `chroot-git` as well.
But even if split single `/usr/bin/git` out of git (to provide e.g.
git-core), it still have dependencies on libpcre2.

Not sure if the added dependencies to base-chroot annoys anyone.


-- 
Danh


  parent reply	other threads:[~2020-04-22  0:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 16:25 [PR PATCH] " sgn
2020-04-21 16:43 ` xtraeme
2020-04-22  0:01 ` sgn [this message]
2020-04-22  0:44 ` sgn
2020-04-22  0:49 ` [PR PATCH] [Updated] " sgn
2020-04-22  0:51 ` sgn
2020-04-22  0:51 ` sgn
2020-04-22 15:07 ` [PR PATCH] [Updated] " sgn
2020-04-22 16:00 ` sgn
2020-04-22 16:14 ` sgn
2020-04-22 16:15 ` sgn
2020-04-22 16:28 ` sgn
2020-04-22 16:30 ` sgn
2020-04-22 16:41 ` Piraty
2020-04-26  1:19 ` [PR PATCH] [Updated] " sgn
2020-04-26  1:20 ` sgn
2020-04-26  7:53 ` Piraty
2020-05-18 11:49 ` [PR PATCH] [Updated] " sgn
2020-05-19 12:26 ` sgn
2020-05-19 13:19 ` sgn
2020-05-23  6:59 ` [PR PATCH] [Merged]: " sgn
2020-05-23 12:25 ` Piraty

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=20200422000123.370ozhtb5SPrgidoS4RKZ8IASMRplCYR8PMm_LNyaUI@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).