9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
Cc: 9fans <9fans@9fans.net>
Subject: Re: [9fans] APL
Date: Wed, 24 Feb 2021 14:48:32 +0100	[thread overview]
Message-ID: <20210224134832.3XTkD%steffen@sdaoden.eu> (raw)
In-Reply-To: <0903a00d50966fc2@orthanc.ca>

Lyndon Nerenberg (VE7TFX/VE6BBM) wrote in
 <0903a00d50966fc2@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):

Traffic size is a real issue for me.
(As is quality of the rtw88 driver of Linux 5.10.*, as is the fact
that git i think still cannot resume failed clones.  I anyway had
lots and lots of trouble and yes grief due to this, here.)

 |Okay, so what's the magic incantation to clone just that subset
 |of branches?  git-clone(1) is not helpful ...

Backward compatible for "the one real git" is

 $ cd DIR; git init
 $ git remote add origin -t BRANCH1 -t BRANCH2 -t 'release/*' URL
 $ git fetch -v

Or git init and then copy the snippet :)
(Mind you, just a few weeks ago on FreeBSD it turned out that
i should re-learn git from scratch.  I turned to it around
2010/11, wrote some scripts and aliases, and unless they break,
for example due to rev-list reverting output in about 2013, i have
a very basic way of doing, lots of update-ref and such, for
example.)

And sorry for the late reply, after weeks of -11° Celsius and
months of winter we had 31° more yesterday, including sunshine,
and i went for cycling.  Then someone reported a brain-damage of
mine in software i maintain, and i had to make a release, and then
it was about 3 o'clock in the morning.

--steffen
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T476a1d7b83269775-Mded9eca8705205b15d2110ca
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2021-02-24 13:49 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
2021-02-24 13:48                   ` Steffen Nurpmeso [this message]
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=20210224134832.3XTkD%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=9fans@9fans.net \
    --cc=lyndon@orthanc.ca \
    /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).