public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: yac@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Official way to do rolling update (Was: Re: Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec)
Date: Mon, 4 Nov 2013 13:12:11 +0100	[thread overview]
Message-ID: <20131104131211.1a776552@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20131104112632.0c7ff3de@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]

On Mon, 4 Nov 2013 11:26:32 +0100
yac <yac@gentoo.org> wrote:

> On Mon, 4 Nov 2013 09:51:32 +0000 (UTC)
> Duncan <1i5t5.duncan@cox.net> wrote:
> 
> > FWIW, I have a whole set of short, often 2-4 letter aliases/scripts
> > that take care of the various options
>
> Sooo, basicly you have defined buttload of aliases, somehow managed to
> remember these nonsensical names and actually did not save any
> keystrokes, because most linux users heard of tab completion and use
> it succesfuly to complete commands and their arguments. Cool story
> bro.

Cool story guys.

Just like how MSOffice 2007 had tons of shortcuts to remember whereas
they got rid of that in MSOffice 2010 by intuitive context relevant
shortcuts; yet, people had memorized the shortcuts and are much quicker
than having to learn all the positions in the new intuitive Ribbon bar.
I didn't learn those shortcuts; so, I am quick with the Ribbon bar...

Or why do

    ebuild name-1.ebuild clean manifest unpack
    ebuild name-2.ebuild clean manifest unpack
    diff -urN /var/tmp/portage/name-{1,2}/workdir/*
    # ^ Actually, you would need to source S="..." twice.

which requires a ton of tabs when I can just do `ediff 1 2`? I can
memorize it, but perhaps others need more short commands and can't.

You'll find out that people end up using both approaches; so, please
let's not get into detailed opinions, it is just a matter of choice.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-11-04 12:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  4:15 Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) yac
2013-11-04  8:50 ` Daniel Campbell
2013-11-04  9:51   ` [gentoo-dev] Re: Official way to do rolling update (Was: " Duncan
2013-11-04 10:26     ` yac
2013-11-04 12:06       ` Dale
2013-11-04 12:28         ` Tom Wijsman
2013-11-04 15:50           ` Rich Freeman
2013-11-04 20:02           ` Dale
2013-11-04 20:27             ` Tom Wijsman
2013-11-04 21:47               ` Dale
2013-11-04 23:28           ` Alan McKinnon
2013-11-04 12:12       ` Tom Wijsman [this message]
2013-11-04 22:28       ` Duncan
2013-11-04 11:17     ` Martin Vaeth
2013-11-04 21:46       ` Duncan
2013-11-05  1:23         ` Michael Orlitzky
2013-11-05  7:51           ` Duncan
2013-11-05 16:21         ` Daniel Campbell
2013-11-04 21:53     ` Peter Stuge
2013-11-04 11:07 ` Official way to do rolling update (Was: Re: [gentoo-dev] " Tom Wijsman

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=20131104131211.1a776552@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=yac@gentoo.org \
    /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