mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Mon, 2 Jan 2017 13:25:16 -0500	[thread overview]
Message-ID: <20170102182516.GC1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170102181535.GB31400@openwall.com>

On Mon, Jan 02, 2017 at 07:15:35PM +0100, Solar Designer wrote:
> On Mon, Jan 02, 2017 at 11:58:32AM -0500, Rich Felker wrote:
> > My experiences with github have been a constant fight with the tools
> > rather than having them make things go more smoothly. I don't like the
> > weight of the web ui (it's very slow on all systems I access it on), I
> > don't like that it doesn't work properly from mobile browsers (e.g.
> > line-number links to source files don't work), I don't like how much
> > you have to click through to get to the history of a given file or to
> > get a link to a specific version, I don't like that it's impossible to
> > review large diffs in the web ui (they just timeout loading), etc. I
> > also don't like everything they do to make it hard to use FF pulls.
> 
> I am no GitHub expert (am not even much of a user), and based on my
> (very limited) experience with it so far I agree with your criticism of
> it, but FWIW I recently found that "to get a link to a specific version"
> you simply need to press "y":
> 
> https://help.github.com/articles/getting-permanent-links-to-files/
> 
> "When viewing a file on GitHub, you can press the "y" key to update the
> URL to a permalink to the exact version of the file you see."
> 
> and I actually made use of this on a few occasions already.  There are
> other keyboard shortcuts as well.  As the page above says:
> 
> "Tip: Press "?" on any page in GitHub to see all available keyboard
> shortcuts."

Thanks for the tip! Proving once again that the fastest way to get a
solution to a problem is to claim in public that it's not possible...
;-)

Rich


  reply	other threads:[~2017-01-02 18:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02  2:31   ` Rich Felker
2017-01-02  2:33     ` Rich Felker
2017-01-02  5:32     ` A. Wilcox
2017-01-02  5:40       ` Rich Felker
2017-01-02  6:39 ` Khem Raj
2017-01-02 16:58   ` Rich Felker
2017-01-02 18:11     ` Alexander Monakov
2017-01-02 18:23       ` Rich Felker
2017-01-02 18:15     ` Solar Designer
2017-01-02 18:25       ` Rich Felker [this message]
2017-01-02 18:27   ` Kurt H Maier
2017-01-02 18:36     ` Rich Felker
2017-01-02 18:52       ` Kurt H Maier
2017-01-02 19:16         ` Rich Felker
2017-01-02 20:06           ` Kurt H Maier
2017-01-02 22:59             ` A. Wilcox
2017-01-02 23:09               ` Kurt H Maier
2017-01-02 19:10       ` Matias A. Fonzo
2017-01-02 19:18         ` Rich Felker
2017-01-02 19:28           ` Matias A. Fonzo
2017-01-03  1:20             ` Laurent Bercot

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=20170102182516.GC1555@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).