From: Bakul Shah <bakul@iitbombay.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] APL
Date: Mon, 22 Feb 2021 21:16:16 -0800 [thread overview]
Message-ID: <40A2A84C-01ED-4F64-91F8-A71F6613BC14@iitbombay.org> (raw)
In-Reply-To: <1FC6618E185274FED11B1F2C8063F969@eigenstate.org>
> On Feb 22, 2021, at 8:41 PM, ori@eigenstate.org wrote:
>
> Quoth Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca>:
>> Steffen Nurpmeso writes:
>>
>>> It can even be as small as
>>>
>>> #?0|kent:unix-hist$ du -sh .
>>> 179M .
>>>
>>> when not including all the new FreeBSD things (for which i at
>>> least track the FreeBSD git repository directly):
>>
>> Okay, so what's the magic incantation to clone just that subset
>> of branches? git-clone(1) is not helpful ...
>>
>> --lyndon
>
> On unix, this should do it:
>
> git clone --single-branch \
> --branch Research-V4-Snapshot-Development \
> https://github.com/dspinellis/unix-history-repo
>
> On plan 9, hot off the press:
>
> git/clone -b $branch \
> https://github.com/dspinellis/unix-history-repo
>
> Unfortunately, git9 has no fetch specs, so keeping a
> *set* of branches will be a bit clunky
For multiple branches try something like the following:
git clone https://github.com/dspinellis/unix-history-repo.git --depth 1 -b Epoch
Without the --depth 1 flag git insists on fetching all 1.9GB of git objects!
But +fetch= lines in .git/config's are not fixed up. As these branches are not
likely to change, that is probably ok.
Next run the following, editing out the branches you don't want.
This list is everything except FreeBSD branches. Amounts to 188MB.
git fetch origin 386BSD-0.0-Snapshot-Development:386BSD-0.0-Snapshot-Development\
386BSD-0.1-Snapshot-Development:386BSD-0.1-Snapshot-Development\
386BSD-0.1-patchkit:386BSD-0.1-patchkit\
386BSD-0.1-patchkit-Import:386BSD-0.1-patchkit-Import\
386BSD-Release:386BSD-Release\
BSD-1-Snapshot-Development:BSD-1-Snapshot-Development\
BSD-2-Snapshot-Development:BSD-2-Snapshot-Development\
BSD-3-Snapshot-Development:BSD-3-Snapshot-Development\
BSD-4-Snapshot-Development:BSD-4-Snapshot-Development\
BSD-4_1_snap-Snapshot-Development:BSD-4_1_snap-Snapshot-Development\
BSD-4_1c_2-Snapshot-Development:BSD-4_1c_2-Snapshot-Development\
BSD-4_2-Snapshot-Development:BSD-4_2-Snapshot-Development\
BSD-4_3-Snapshot-Development:BSD-4_3-Snapshot-Development\
BSD-4_3_Net_1-Snapshot-Development:BSD-4_3_Net_1-Snapshot-Development\
BSD-4_3_Net_2-Snapshot-Development:BSD-4_3_Net_2-Snapshot-Development\
BSD-4_3_Reno-Snapshot-Development:BSD-4_3_Reno-Snapshot-Development\
BSD-4_3_Tahoe-Snapshot-Development:BSD-4_3_Tahoe-Snapshot-Development\
BSD-4_4-Snapshot-Development:BSD-4_4-Snapshot-Development\
BSD-4_4_Lite1-Snapshot-Development:BSD-4_4_Lite1-Snapshot-Development\
BSD-4_4_Lite2-Snapshot-Development:BSD-4_4_Lite2-Snapshot-Development\
BSD-Release:BSD-Release BSD-SCCS:BSD-SCCS\
Bell-32V-Snapshot-Development:Bell-32V-Snapshot-Development\
Bell-Release:Bell-Release Research-PDP7-Snapshot-Development:Research-PDP7-Snapshot-Development\
Research-Release:Research-Release\
Research-V1-Snapshot-Development:Research-V1-Snapshot-Development\
Research-V2-Snapshot-Development:Research-V2-Snapshot-Development\
Research-V3-Snapshot-Development:Research-V3-Snapshot-Development\
Research-V4-Snapshot-Development:Research-V4-Snapshot-Development\
Research-V5-Snapshot-Development:Research-V5-Snapshot-Development\
Research-V6-Snapshot-Development:Research-V6-Snapshot-Development\
Research-V7-Snapshot-Development:Research-V7-Snapshot-Development\
usr/src/BSD-SCCS-Import:usr/src/BSD-SCCS-Import
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T476a1d7b83269775-M164190580e3d2b269501e9f0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-02-23 5:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:31 Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-21 23:01 ` Skip Tavakkolian
2021-02-21 23:19 ` Kurt H Maier
2021-02-22 1:24 ` Bakul Shah
2021-02-22 16:53 ` jas
2021-02-22 17:46 ` arnold
2021-02-22 18:28 ` tlaronde
2021-02-22 20:35 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-22 21:44 ` Charles Forsyth
2021-02-23 8:14 ` tlaronde
2021-02-23 8:58 ` arnold
2021-02-23 9:20 ` tlaronde
2021-02-23 9:57 ` arnold
2021-02-23 10:09 ` tlaronde
2021-02-23 7:57 ` tlaronde
2021-02-22 22:01 ` Bakul Shah
2021-02-22 22:43 ` Charles Forsyth
2021-02-22 23:09 ` Bakul Shah
2021-02-22 23:56 ` Charles Forsyth
2021-02-23 0:13 ` Bakul Shah
2021-02-23 0:03 ` Steffen Nurpmeso
2021-02-23 0:47 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-23 4:41 ` ori
2021-02-23 5:11 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-23 5:16 ` Bakul Shah [this message]
2021-02-24 13:48 ` Steffen Nurpmeso
2021-03-08 22:11 ` Jerome Ibanes
2021-02-24 0:33 Lyndon Nerenberg (VE7TFX/VE6BBM)
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=40A2A84C-01ED-4F64-91F8-A71F6613BC14@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=9fans@9fans.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.
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).