git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Willhelm Busch" <willhelm.busch@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: Questions about git-rev-parse
Date: Wed, 28 Feb 2007 21:16:09 -0500	[thread overview]
Message-ID: <a51a02b80702281816j1ff9d42i5fc680752c515082@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702271905200.12485@woody.linux-foundation.org>

On Tue, Feb 27, 2007 at 07:19:54PM -0800, Linus Torvalds wrote:
> On Tue, 27 Feb 2007, Theodore Ts'o wrote:
> >
> > So I was looking at git-rev-parse trying to understand the man page, as
> > I was trying to understand how various commands can accept lists (or
> > ranges) of commits, and the man page raised a number of questions.
> > First of all, the DESCRIPTION section doesn't quite parse as English:
> >
> >        Many  git  porcelainish commands take mixture of flags (i.e. parameters
> >        that  begin  with  a  dash  -)  and  parameters  meant  for  underlying
> >        git-rev-list  command  they use internally and flags and parameters for
> >        other commands they use as the downstream of git-rev-list.
> >
> > But, as best as I can gather that it's a helper function meant to do
> > some basic options parsing for those git porcelain commands that expect
> > to take a set of revision ID's.
>
> Heh. This is totally due to hysterical raisins.

When it comes to dancing time
 At the branch of the grapevine
Out pop many lively souls,
 From their seed pods, shells, and holes.

'Twas one balmy summer's night
 When some documents to write
Linus rested on the ground
 Near the dancers' cheery round.

Heedless of their drunken rages,
 He cranked out a few man pages,
As he started git-rev-parse,
 Came a merry nighttime farce.

When by wine they are made merry
 Certain fruits wax literary,
Writing nonsense as they please --
 Raisins are the worst of these.

They seized Linus as their chance.
 "Let us leave this odious dance!"
With a hysterical hop,
 Down they jumped, to his laptop!

As they made a small edit,
 Typed the raisins: "git commit"!
"Could my shell prompt be possessed?"
 Linus wondered, much distressed.

Linus scratched his Nordic pate.
 "I should not be up this late!
Coffee's addling my sight!
 Better finish for tonight."

In the main I'm laudatory
 Of the git repository.
It has weirdness and to spare,
 But the raisins put it there.

      reply	other threads:[~2007-03-01  2:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28  2:23 Questions about git-rev-parse Theodore Ts'o
2007-02-28  2:40 ` Junio C Hamano
2007-02-28  2:52   ` Theodore Tso
2007-02-28  3:33     ` Linus Torvalds
2007-02-28  6:40       ` Theodore Tso
2007-02-28  8:54       ` Andy Parkins
2007-02-28 16:00         ` Linus Torvalds
2007-02-28  3:19 ` Linus Torvalds
2007-03-01  2:16   ` Willhelm Busch [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=a51a02b80702281816j1ff9d42i5fc680752c515082@mail.gmail.com \
    --to=willhelm.busch@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).