Date: Thu, 01 Apr 2021 12:32:52 +0200 From: Jimmy Renner <jimbo@renner.se> To: freebsd-ports@freebsd.org Subject: Re: No update for a day on ports? Message-ID: <20210401123252.Horde.7_V-YzZYK_DrzF7Cah4DzY-@renner.se> In-Reply-To: <20210401095527.7de7a28e@raksha.tavi.co.uk> References: <20210401082247.668e4394@zeta.dino.sk> <YGV0EvmP3Hkk5543@mail.bsd4all.net> <3b7de439-12a1-70a4-7aec-8b2a9fde38ba@heuristicsystems.com.au> <20210401095527.7de7a28e@raksha.tavi.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Citerar Bob Eager <rde@tavi.co.uk>:
> On Thu, 1 Apr 2021 19:47:01 +1100
> Dewayne Geraghty <dewayne@heuristicsystems.com.au> wrote:
>
>> Would appreciate if anyone can provide insight as to the 4 git
>> commands that I need to function, in a manner similar to the way I
>> use svnlite use. Git equivalents for:
>>
>> svnlite update /usr/ports
>> svnlite update -r '{$YYYY-$MM-$DD}' /usr/ports/$category/$port
>> svnlite log -l $N /usr/ports/$category/$port
>> svnlite diff /usr/ports/$category/$port
>
> I got a partial answer. There is a port, net/gitup, that will do an
> update of sorts. (Note: I was just told 'gitup' and there is an old
> port, now renamed 'git-up', which is not the right one).
>>
>> I'm sure many other users would have a similar usage (and similar
>> non-knowledge of git)
>
> Indeed. I feel this should have been done in advance. And been in
> Appendix A of the Handbook in plenty of time.
>
>> As a minor aside, has anyone stated the reason why the user-base of
>> base or ports are moving to git?
>
> Going with the fashion, IMO. But I will no doubt get shouted down.
>
If it is deprecated where do I find the information I need, this does
not help:
https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/ports-using.html
Cheers, Jimmy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210401123252.Horde.7_V-YzZYK_DrzF7Cah4DzY->