From: Denton Liu <liu.denton@gmail.com>
To: Birger Skogeng Pedersen <birger.sp@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Pratyush Yadav <me@yadavpratyush.com>,
Git List <git@vger.kernel.org>,
Bert Wesarg <bert.wesarg@googlemail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Philip Oakley <philipoakley@iee.email>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: RFC: Moving git-gui development to GitHub
Date: Thu, 24 Oct 2019 10:16:16 -0700 [thread overview]
Message-ID: <20191024171616.GA40755@generichostname> (raw)
In-Reply-To: <CAGr--=JQXfbJaxvYo1ue__eRHyEgKDd3mjTgxXxT=7seTU_oYA@mail.gmail.com>
On Thu, Oct 24, 2019 at 09:37:08AM +0200, Birger Skogeng Pedersen wrote:
> - It's a lot easier to get a total overview of all issues. Especially
> useful when you'd want to see open issues. Pratyush mentions he has a
> text-file on his computer where he lists all the currently open
> issues. We can't see this text-file. And even if we could, we'd still
> have to navigate the mail archives to find the discussions and read
> the emails one page at a time.
I also had one of these text files laying around with my TODOs. Dscho
mentioned to me a while back that it might be a good idea to move
everything to GitGitGadget's issues. It's worked out pretty well for me
so far and I think a couple people have even picked up some work off of
there. It might be worth considering moving issues to either git-gui's
or GitGitGadget's repo.
If anything, it's no worse than the current situation since if GitHub
goes down for whatever reason, then Pratyush's list of issues is private
again. But as long as GitHub is up, then it'd be nice to have a public
list of issues for people to work on.
next prev parent reply other threads:[~2019-10-24 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:13 RFC: Moving git-gui development to GitHub Pratyush Yadav
2019-10-24 2:06 ` Junio C Hamano
2019-10-24 7:37 ` Birger Skogeng Pedersen
2019-10-24 17:16 ` Denton Liu [this message]
2019-10-24 19:06 ` Pratyush Yadav
2019-10-24 21:29 ` Pratyush Yadav
2019-10-25 5:33 ` Birger Skogeng Pedersen
2019-10-25 17:47 ` Pratyush Yadav
2019-10-24 19:46 ` Elijah Newren
2019-10-25 18:36 ` Pratyush Yadav
2019-10-26 18:25 ` Jakub Narebski
2019-10-28 10:13 ` Konstantin Ryabitsev
2019-10-30 6:21 ` Elijah Newren
2019-11-20 12:19 ` Birger Skogeng Pedersen
2019-11-20 17:13 ` Elijah Newren
2021-04-19 20:33 ` Pain points in PRs [was: Re: RFC: Moving git-gui development to GitHub] SZEDER Gábor
2021-04-19 21:52 ` Junio C Hamano
2021-04-20 7:49 ` Son Luong Ngoc
2021-04-20 20:17 ` Junio C Hamano
2021-04-22 20:22 ` Felipe Contreras
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=20191024171616.GA40755@generichostname \
--to=liu.denton@gmail.com \
--cc=bert.wesarg@googlemail.com \
--cc=birger.sp@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmx.de \
--cc=me@yadavpratyush.com \
--cc=philipoakley@iee.email \
/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).