From: Greg Stark <gsstark@mit.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Greg Stark <gsstark@mit.edu>, Adrian Bunk <bunk@stusta.de>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [SATA] libata-dev queue updated
Date: 04 Jun 2005 22:25:17 -0400 [thread overview]
Message-ID: <87k6l9k0aa.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20050604191958.GA13111@havoc.gtf.org>
Jeff Garzik <jgarzik@pobox.com> writes:
> On Sat, Jun 04, 2005 at 03:15:24PM -0400, Greg Stark wrote:
> > So my question is, if I did tackle this riddle trail and figured out how to
> > fetch the passthru branch against 2.6.12, what would it buy me? Would SMART
> > just start working? Or would it just confuse the SMART tools until they're
> > updated? Or would it just crash my machine?
>
> SMART should just start working. It adds the ioctls that existing smartd
> and hdparm already know about.
So, uh, where do I get git? Where is your "git repository" and Linus' "git
repository" and how do I set that up?
Or, at least, where do I find all this info?
I take it it's not this:
Package: git
Priority: optional
Section: utils
Installed-Size: 919
Maintainer: Ian Beckwith <ianb@nessie.mcc.ac.uk>
Architecture: i386
Version: 4.3.20-7
Depends: libc6 (>= 2.3.2.ds1-4), libncurses5 (>= 5.4-1), libreadline4 (>= 4.3-1)
Filename: pool/main/g/git/git_4.3.20-7_i386.deb
Size: 261822
MD5sum: a708688e17259ed1e99d2828e1acb3f6
Description: GNU Interactive Tools, a file browser/viewer and process viewer/killer
git (GNU Interactive Tools) is a set of interactive text-mode tools,
closely integrated with the shell. It contains an extensible file
system browser, an ascii/hex file viewer, a process viewer/killer and
some other related utilities and shell scripts. It can be used to
increase the speed and efficiency of most of the daily tasks such as
copying and moving files and directories, invoking editors,
compressing and uncompressing files, creating and expanding archives,
compiling programs, sending mail, etc. It looks nice, has colors (if
the standard ANSI color sequences are supported) and is user-friendly.
.
One of the main advantages of Git is its flexibility. It is not
limited to a given set of commands. The configuration file can be
easily enhanced, allowing the user to add new commands or file
operations, depending on its needs or preferences.
--
greg
next prev parent reply other threads:[~2005-06-05 2:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 6:08 [SATA] libata-dev queue updated Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48 ` Jeff Garzik
2005-06-04 18:50 ` Adrian Bunk
2005-06-04 19:05 ` Jeff Garzik
2005-06-04 19:15 ` Greg Stark
2005-06-04 19:19 ` Jeff Garzik
2005-06-05 2:25 ` Greg Stark [this message]
2005-06-05 2:30 ` Jeff Garzik
2005-06-05 5:30 ` Greg Stark
2005-06-22 16:15 ` Mark Lord
2005-06-22 20:23 ` Jeff Garzik
2005-06-23 3:39 ` Mark Lord
2005-06-05 2:40 ` Drew Winstel
2005-06-05 2:58 ` Jim Crilly
2005-06-06 16:01 ` Mark Lord
2005-06-07 1:57 ` Greg Stark
2005-06-07 11:20 ` Brad Campbell
2005-06-08 8:33 ` Mark Lord
2005-06-07 13:15 ` Brad Campbell
2005-06-08 8:37 ` Mark Lord
2005-06-07 13:51 ` Greg Stark
2005-06-08 10:30 ` Mark Lord
2005-06-08 8:51 ` Mark Lord
2005-06-07 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 7:00 Bene Martin
2005-03-10 5:40 Jeff Garzik
2005-03-29 9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
2005-03-02 2:40 Jeff Garzik
2005-02-19 8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09 ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-30 16:15 Jeff Garzik
2004-10-27 6:52 Jeff Garzik
2004-10-27 6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03 ` Jeff Garzik
2004-10-18 23:52 Jeff Garzik
2004-10-16 0:44 Jeff Garzik
2004-10-15 8:04 Jeff Garzik
2004-10-15 17:15 ` Jeff Garzik
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=87k6l9k0aa.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).