Git development
 help / color / mirror / Atom feed
From: Taylor Hedberg <tmhedberg@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>,
	Joshua Juran <jjuran@gmail.com>,
	Daniel Searles <dsearles@medialab.com>,
	git@vger.kernel.org, oleganza@gmail.com
Subject: Re: Gitbox
Date: Wed, 13 Apr 2011 16:26:28 -0400	[thread overview]
Message-ID: <20110413202627.GD11019@foodlogiq3-xp-d620> (raw)
In-Reply-To: <1302725089.22408.11.camel@drew-northup.unet.maine.edu>

Drew Northup, Wed, Apr 13, 2011 at 04:04:49PM -0400:
> If that's what he's doing then why does he state that the git binaries
> are "for your convenience only"--strongly implying his program will
> work in the absence thereof? I'm hoping he just made a typo--as what
> he said is there in plain English, and is somewhat contradicted by the
> next sentence. If he's indeed using the plumbing then the binaries are
> required--which is indeed what they are there for. 

I didn't detect that implication at all. I took it to mean that he is
distributing Git alongside his frontend because it would not function
properly without it. It's a "convenience" in the sense that if he didn't
bundle the Git binaries, you'd have to install them separately in order
to use his product. Why would he bother to include Git itself if the
product worked just fine without it?


> I think that I've already proved myself to be one of the list's
> resident grammar nazis. If you wish to dispute my interpretation of
> his grammar please contact me directly and don't bother the rest of
> the list.

Sending this to the list anyway, because it seems germane to the overall
discussion.

  reply	other threads:[~2011-04-13 20:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 18:16 Gitbox Daniel Searles
2011-04-13 18:55 ` Gitbox Joshua Juran
2011-04-13 18:59 ` Gitbox Drew Northup
2011-04-13 19:09   ` Gitbox Joshua Juran
2011-04-13 19:16     ` Gitbox Drew Northup
2011-04-13 19:24       ` Gitbox Joshua Juran
2011-04-13 19:41       ` Gitbox Randal L. Schwartz
2011-04-13 20:04         ` Gitbox Drew Northup
2011-04-13 20:26           ` Taylor Hedberg [this message]
2011-04-13 20:29           ` Gitbox Joshua Juran
2011-04-13 22:56           ` Gitbox Tim Smith
2011-04-14  9:52           ` Gitbox Sitaram Chamarty
2011-04-14 10:03             ` Gitbox Vincent van Ravesteijn
2011-04-14 12:34             ` Gitbox Drew Northup
2011-04-13 20:43         ` Gitbox Junio C Hamano
     [not found]           ` <1C18B4FB-BB10-4AC7-8952-D477CB4EF289@medialab.com>
2011-04-13 22:13             ` Gitbox Randal L. Schwartz
2011-04-13 23:10           ` Gitbox Randal L. Schwartz
2011-04-13 19:18 ` Gitbox Jakub Narebski
     [not found] <BANLkTikfCDm-5Yde=2Cm-ROc1dcMwopvOg@mail.gmail.com>
2011-04-13 22:23 ` Gitbox Joshua Juran
2011-04-14  1:58   ` Gitbox Chris Perkins
2011-04-14  2:02     ` Gitbox Randal L. Schwartz
2011-04-14  2:28     ` Gitbox Chris Perkins
2011-04-14  2:34       ` Gitbox Randal L. Schwartz
2011-04-14  4:59       ` Gitbox Joshua Juran
2011-04-14 13:55     ` Gitbox Martin Langhoff
     [not found]     ` <32803572.1897.1302789371873.JavaMail.trustmail@mail1.terreactive.ch>
2011-04-14 14:15       ` Gitbox Victor Engmark
2011-04-14 14:52         ` Gitbox Martin Langhoff
2011-04-15 19:21     ` Gitbox Tim Smith

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=20110413202627.GD11019@foodlogiq3-xp-d620 \
    --to=tmhedberg@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=dsearles@medialab.com \
    --cc=git@vger.kernel.org \
    --cc=jjuran@gmail.com \
    --cc=merlyn@stonehenge.com \
    --cc=oleganza@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox