The Git List <[email protected]> has some strict anti-spam / anti-bloat
rules.
The emails must be plain text, absolutely no HTML, no banned words. Plus
there appears to be an initial moderation of a few hours (up to a day?).
The hardest bit is ensuring plain text. And the list uses 'reply all' so
that those not subscribed are included.
I just posted a reply to the thread in the Git list,
https://public-inbox.org/git/C89EEDA4D8F84C6290111C04ADAE6872@PhilipOakley/
on my thoughts.
Philip
----- Original Message -----
From: "vit via Git for human beings" <[email protected]>
To: "Git for human beings" <[email protected]>
Sent: Thursday, November 30, 2017 4:13 PM
Subject: [git-users] Re: How hard would it be to implement sparse
fetching/pulling?
Konstantin, thanks for mentioning that. Unfortunately I've asked a
question
here first and mail server didn't let me send a link to this thread.
Jeff, thanks, that's super exciting. I will check it out.
Is it best to continue discussion here as this thread has all relevant
context?
On Thursday, November 30, 2017 at 7:54:46 AM UTC-8,
[email protected] wrote:
This question was cross-posted on the main git mailing list.
For completeness with the git-users mailing list here.
The following describes info on the work-in-progress for this feature.
*https://public-inbox.org/git/[email protected]/*
<https://public-inbox.org/git/[email protected]/>
--
You received this message because you are subscribed to the Google Groups
"Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
