From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: github hygiene
Date: Thu, 19 Jul 2018 10:30:00 +0200 [thread overview]
Message-ID: <20180719103000.5302c8bb@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <dd7b190e-ccee-ae6d-e0b5-6fbd0328a5f3@ilbers.de>
Am Wed, 18 Jul 2018 13:00:22 +0300
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Hi all,
>
> At the moment we have 4 active branches on isar github:
>
> 'next'
> 'mosipov-next'
> 'asmirnov/devel'
> 'ibr/devel'
>
> We have a number of stale branches (see list below).
> I'm going to archive them on our local server and after that
> remove them on github. If you have any objections please let me know.
Looks good to me. I would even suggest to call mosipov-next
mosipov/devel to be consistent with the other two dev-branches.
> Kind regards,
> Maxim.
>
> List of stale branches:
>
> 'develop' Updated 2 years ago by flenorm
> 'custom_kernel' Updated a year ago by flenorm
> 'custom_uboot' Updated a year ago by flenorm
> 'i386' Updated a year ago by flenorm
> 'lenormf/bincache-20170331' Updated a year ago by lenormf
> 'lenormf/uefi_wic_amd64-20170428' Updated a year ago by ismagulb
> 'lenormf/develop-l20170602-dpkg-cross' Updated a year ago by ismagulb
> 'asmirnov/tmp' Updated 10 months ago by alexbluesman
> 'asmirnov/proot' Updated 9 months ago by alexbluesman
> 'asmirnov/build_rep' Updated 8 months ago by alexbluesman
> 'build_rep' Updated 7 months ago by alexbluesman
> 'ibr/20171231-3-avocado' Updated 7 months ago by ismagulb
> 'asmirnov/next' Updated 5 months ago by jan-kiszka
You could also leave tags on them, to archive them on github. Given
that will not make them show up as a "release". There might still be
value in them, maybe the people that created them should give their OK.
Henning
>
> On 06/28/2018 06:45 PM, Henning Schild wrote:
> > Hi,
> >
> > this morning i had a look at the isar github site again, and it
> > seems to be in a pretty outdated state.
> > It has a ton of dead branches that should better be kept in clones
> > of the authors. And the issues seem like they have not been looked
> > at for quite some time.
> >
> > I would suggest to revisit those issues and close them, and to get
> > rid of some of those branches. We might hardly ever look on github,
> > but others will. And the first impression often counts.
> >
> > Henning
> >
>
>
prev parent reply other threads:[~2018-07-19 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 15:45 Henning Schild
2018-07-18 10:00 ` Maxim Yu. Osipov
2018-07-19 8:30 ` Henning Schild [this message]
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=20180719103000.5302c8bb@md1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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