From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Carl Worth <cworth@cworth.org>, git@vger.kernel.org
Subject: Re: A tour of git: the basics (and notes on some unfriendly messages)
Date: Sat, 29 Sep 2007 01:49:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709290144310.28395@racer.site> (raw)
In-Reply-To: <20070929000056.GZ3099@spearce.org>
Hi,
On Fri, 28 Sep 2007, Shawn O. Pearce wrote:
> On Cygwin we have man, so `git help init` (or `git init --help`) work
> just fine to display the manual entry. No idea about the MSYS port.
We open the html pages. That is, we don't yet, since we do not generate
the html pages just yet; asciidoc is a Python program, and Python is not
available as an MSys program as far as I know (and asciidoc insists on
finding files in a Unix-like file structure, so we _do_ need an MSys
Python).
... but all this would be easier if we succeeded in having a minimal
asciidoc lookalike in git.git...
> > * The output from a git-clone operating locally is really confusing:
> >
> > $ git clone hello hello-clone
> > Initialized empty Git repository in /tmp/hello-clone/.git/
> > 0 blocks
> >
> > Empty? Didn't I just clone it? What does "0 blocks" mean?
>
> Yea. That's because we realized its on the local disk and used
> `cpio` with hardlinks to copy the files. So cpio says it copied
> 0 blocks as it actually just hardlinked everything for you. No
> data was actually copied.
>
> git-gui's new clone UI uses fancy progress meters here and tries
> to shield the user from "plumbing and UNIX tools" spitting out
> seemingly nonsense messages. We probably should try harder in
> git-clone to do the same here.
AFAICT git-clone is a prime candidate for builtinification, after which
issues like this should be easy to address.
> > * git-log by default displays "Date" that is the author date, but
> > also only uses committer date for options such as --since. This is
> > confusing.
>
> I've never thought about that. But when you say it I think its very
> obvious that it could be confusing to a new user. Maybe we should show
> the committer line and its date if it doesn't match the author
> name/date. Usually I don't care who committed a change in git.git (its
> a very small handful of people that Junio pulls from directly) but at
> day-job committer name is usually just as interesting as the author name
> *when they aren't the same*.
--pretty=fuller
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-29 0:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 23:07 A tour of git: the basics (and notes on some unfriendly messages) Carl Worth
2007-09-29 0:00 ` Shawn O. Pearce
2007-09-29 0:49 ` Johannes Schindelin [this message]
2007-09-29 7:44 ` Steffen Prohaska
2007-09-29 15:06 ` Johannes Schindelin
2007-09-29 16:06 ` Steffen Prohaska
2007-09-29 16:05 ` [PATCH] WinGit: included /bin/start in the installer Steffen Prohaska
2007-09-29 16:05 ` [PATCH] WinGit: include html pages from official git.git's html branch Steffen Prohaska
2007-09-29 20:50 ` Johannes Schindelin
2007-09-29 22:13 ` Junio C Hamano
2007-09-29 23:23 ` Johannes Schindelin
2007-09-30 8:19 ` Steffen Prohaska
2007-09-29 9:01 ` A tour of git: the basics (and notes on some unfriendly messages) Pierre Habouzit
2007-09-29 10:45 ` [RFC] patch series to sketch a less verbose and frightening output Pierre Habouzit
2007-09-29 10:49 ` Pierre Habouzit
[not found] ` <1191062758-30631-2-git-send-email-madcoder@debian.org>
2007-09-29 14:33 ` [PATCH 1/4] Rework progress module so that it uses less screen lines, with progress bars Nicolas Pitre
2007-09-29 16:07 ` Pierre Habouzit
2007-09-30 12:45 ` A tour of git: the basics (and notes on some unfriendly messages) Wincent Colaiuta
2007-09-30 13:49 ` Pierre Habouzit
2007-09-30 14:31 ` Wincent Colaiuta
2007-09-29 21:48 ` Steffen Prohaska
2007-09-29 22:25 ` Junio C Hamano
2007-09-30 8:15 ` Steffen Prohaska
2007-09-30 10:17 ` Junio C Hamano
2007-09-30 12:44 ` Johannes Schindelin
2007-09-30 13:41 ` Steffen Prohaska
2007-09-29 0:45 ` Junio C Hamano
2007-09-30 3:38 ` Carl Worth
2007-09-30 3:38 ` Carl Worth
2007-09-29 5:32 ` Nguyen Thai Ngoc Duy
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=Pine.LNX.4.64.0709290144310.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).