All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alban Gruin <alban.gruin@gmail.com>
To: Birger Skogeng Pedersen <birgersp@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Pratyush Yadav <me@yadavpratyush.com>,
	Harish Karumuthil <harish2704@gmail.com>,
	Git List <git@vger.kernel.org>, David Aguilar <davvid@gmail.com>
Subject: Re: GitGUIGadget, was Re: [PATCH] Feature: custom guitool commands can now have custom keyboard shortcuts
Date: Mon, 7 Oct 2019 21:16:43 +0200	[thread overview]
Message-ID: <86599b38-fe3c-903e-2f52-22cacea06e8d@gmail.com> (raw)
In-Reply-To: <CAGr--=JpC88+Bnc233aJRe1XDgPzZxThxHQShoDobBA6hcYChQ@mail.gmail.com>

Hi Birger,

Le 07/10/2019 à 12:43, Birger Skogeng Pedersen a écrit :
> It seems this topic has kindof derailed(?). But I feel like voicing my
> opinion nonetheless.
> 
> -%<-
> 
> My biggest gripe with not using Github is how to keep track of replies
> (comments) to a topic. I have to navigate through multiple emails to
> get and overview of what everyone has been saying, when it should just
> be a single collection of replies from everyone (like in a Github
> issue). Where each issue has their own thread, and they can be linked
> to each other or to PRs.
> 

I don’t know which email client you use, but they usually have an option
to sort messages by thread -- this is how I handle my git folder with
Thunderbird; it takes one click to switch from plain view to threaded
view, and two to isolate a specific thread.  public-inbox.org also does
this.  Some don’t though, and gmail specifically has weird opinions on
which message is part of which thread.

On the other hand, I don’t really like non-threaded means of
communication, and I am very confused as to why modern services neglect
this feature -- there may be a good reason, I’m not an expert in
human-computer interaction :).  But personally, I find it very hard to
follow issues on github (or even IRC logs, for that matter) when there
is more than 2 people involved.

> 
> Just felt like chiming in,
> Birger
> 
Cheers,
Alban


  reply	other threads:[~2019-10-07 19:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 11:38 [PATCH] Feature: custom guitool commands can now have custom keyboard shortcuts Harish K
2016-03-31 16:41 ` David Aguilar
2016-04-01  6:32   ` harish k
2019-10-03 14:48     ` harish k
2019-10-03 21:44       ` Pratyush Yadav
2019-10-04  8:49         ` Johannes Schindelin
2019-10-04 12:01           ` Pratyush Yadav
2019-10-05 20:16             ` Harish Karumuthil
2019-10-05 21:01               ` Pratyush Yadav
2019-10-06  9:49                 ` Johannes Schindelin
2019-10-06 18:39                   ` Pratyush Yadav
2019-10-06 19:37                     ` Philip Oakley
2019-10-06 20:27                     ` Johannes Schindelin
2019-10-06 21:06                       ` Pratyush Yadav
2019-10-07  9:20                         ` GitGUIGadget, was " Johannes Schindelin
2019-10-07 10:43                           ` Birger Skogeng Pedersen
2019-10-07 19:16                             ` Alban Gruin [this message]
2019-11-19 22:09                         ` Making GitGitGadget's list -> PR comment mirroring bidirectional, " Johannes Schindelin
2019-11-20 14:22                           ` Pratyush Yadav
2019-10-06 22:40                       ` Philip Oakley
2019-10-07  6:22                   ` Harish Karumuthil
2019-10-07 10:01                     ` Johannes Schindelin
2019-10-08 19:31                       ` Harish Karumuthil
2019-10-09 20:42                         ` Johannes Schindelin
2019-10-13 20:09                         ` Pratyush Yadav
2019-10-07  6:13                 ` Harish Karumuthil
2019-10-13 19:17                   ` Pratyush Yadav

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=86599b38-fe3c-903e-2f52-22cacea06e8d@gmail.com \
    --to=alban.gruin@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=birgersp@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=harish2704@gmail.com \
    --cc=me@yadavpratyush.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.