Date: Thu, 16 Jul 2020 11:49:23 -0400 From: Ed Maste <emaste@freebsd.org> To: Dan Langille <dan@langille.org> Cc: freebsd-git@freebsd.org Subject: Re: FreshPorts - git : status up Message-ID: <CAPyFy2A5j=Nu6d2zY9=tVkJLWv10azEo8iP9FtE9YSwxU9V-ig@mail.gmail.com> In-Reply-To: <baf4d6b8-2e3b-4b06-8eb1-73812de97563@www.fastmail.com> References: <baf4d6b8-2e3b-4b06-8eb1-73812de97563@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 Jul 2020 at 17:43, Dan Langille <dan@langille.org> wrote: > > Hello, > > https://devgit.freshports.org/ is improving. Most of the git-specific work is at https://github.com/FreshPorts/git_proc_commit in the git-to-freshports directory. > > There are several issues open, some for documentation purposes, other for tracking. > > What I do need is a better icon for the git link: https://devgit.freshports.org/images/git.png I found the same image without the text at https://upload.wikimedia.org/wikipedia/commons/thumb/3/3f/Git_icon.svg/768px-Git_icon.svg.png > for branches in workingcopy > do > the iteration mentioned above > done > > But not all branches are relevant. Indeed, many are not. I think regexes like '2[0-9]{3}Q[1-4]' for ports and 'stable/[0-9]+' for src are probably sufficient to identify relevant branches; I don't think doc needs any branches.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2A5j=Nu6d2zY9=tVkJLWv10azEo8iP9FtE9YSwxU9V-ig>