Re: updating the git documentation on http://www.kernel.org/pub/software/scm/git/docs/

wanted to send a co-worker a link to the >>'migration from cvs' URL and couldn't find one. >> >> > >Thomas, I suspect you have a wrong David, and would want to ask >David Greaves instead. > > > > quite right. I've dropped out somewh

First git-pasky bug report? :) error: bad signature/verify header failed

Hi I'm just starting to look at git (and cogito). Earlier this morning I got and built http://pasky.or.cz/~pasky/dev/git/git-pasky-base.tar.bz2 I then did a "git pull pasky" and a make. All went well. A couple of hours later I did another git pull pasky and had the problem shown below. I moved t

Add + Status patches

Hi Petr Thankyou for the help earlier - problem resolved. I have a trivial patch (attached). It allows: find src -type f | git add - and fixes git status not reporting added files properly (on my debian system it only reported the first file in .git/add-queue) Should I send this as a patch or as

[PATCH 1/1] add, rm + status patches

because the code in git status is getting pretty ugly. I'd be happy to help with a preliminary port to perl. David Signed-off-by: David Greaves <[EMAIL PROTECTED]> --- Index: README === --- c0aff9b98c4242ab8965c428241df1d8f7a

Re: Add + Status patches

Junio C Hamano wrote: DG> It allows: DG> find src -type f | git add - I am slow today, but have you considered using xargs? yep thanks :) I know you _could_ do it with xargs - but you _could_ use the raw git commands too. This is a "be nice to the user" layer and I was 'surprised' that neithe

Re: Change "pull" to _only_ download, and "git update"=pull+merge?

David A. Wheeler wrote: I propose changing "pull" to ONLY download, and "update" to pull AND merge. Why? It seems oddly inconsistent that "pull" sometimes merges in changes, but at other times it doesn't. true I propose that there be two subcommands, "pull" and "update" (now that "update" isn't a

Re: [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 03:40:54AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... Here is perhaps a better way to provide detailed help for each git command. A command.help file for each command can be written in the style of a man page.

Re: [PATCH] Add help details to git help command. (This time with Perl)

Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 07:35:15PM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... I've been working on git.pl and getting help working nicely things to try: git.pl help git.pl add git.pl add --help git.pl add --man git.pl help add The main

Re: [PATCH] Add help details to git help command. (This time with Perl)

Steven Cole wrote: Speaking of "I think", the name "cogito" was suggested for the SCM layer, but IIRC Linus suggested staying with just plain git. Petr suggested tig, perhaps because it looks at git from another point of view. I haven't read _all_ the mails - I thought cogito was kinda selected and

[PATCH] Some documentation...

ecome man pages... In doing this I noticed a couple of points: * update-cache won't accept ./file or fred/./file * checkout-cache doesn't seem to preserve mode Are these bugs or should they be documented? I've taken the approach of documenting behaviour for now. Signed-of

Re: [PATCH] Some documentation...

C. Scott Ananian wrote: On Wed, 20 Apr 2005, David Greaves wrote: In doing this I noticed a couple of points: * update-cache won't accept ./file or fred/./file The comment in update-cache.c reads: /* * We fundamentally don't like some paths: we don't want * dot or dot-dot anywhe

Re: Git hangs while executing commit-tree

Linus Torvalds wrote: On Wed, 20 Apr 2005, Rhys Hardwick wrote: [EMAIL PROTECTED]:~/repo/tmp.repo$ commit-tree c80156fafbac377ab35beb076090c8320f874f91 Committing initial tree c80156fafbac377ab35beb076090c8320f874f91 At this point, the command seems to be just waiting. That's _exactly_ what it's

Re: [PATCH] Add help details to git help command. (This time with Perl)

We've decided to go for the individual scripts directly. :-) Just to clarify - individual scripts or $0 name handling? I kinda like one big script - also means we don't need to 'install' it to get access to Cogito.pm... Unfortunately, you didn't send the attachments inline, so I can't comment on

Re: [PATCH] Improve usage messages

Petr Baudis wrote: Dear diary, on Thu, Apr 21, 2005 at 02:41:52PM CEST, I got a letter where Matthias Urlichs <[EMAIL PROTECTED]> told me that... This patch adds somewhat-improved usage messages to some of Linus' programs. Specifically, they now handle -? / --help. just so you know, the intention o

[PATCH] Docs update

Added commit-tree, diff-cache and environment info Signed-off-by: David Greaves <[EMAIL PROTECTED]> --- Index: README.reference === --- c0260bfb82da04aeff4e598ced5295d6ae2e262d/README.reference (mode:100644

Re: [PATCH] Docs update

Petr Baudis wrote: Make a choice - either you are describing git or Cogito. The frmer has no RSYNC_FLAGS and does not care about any heads or anything at all (you might mention it as a recommended convention, though). I was going to do both - surely that's OK? The only reason it's core so far is th

Re: [PATCH] Docs update

Junio C Hamano wrote: "DG" == David Greaves <[EMAIL PROTECTED]> writes: Looks nice. I agree with Petr's comment that separating core part and Cogito part would be good OK And the option to use working tree is not having the --cached flag you describe later. Please also up

wit suggestion

Hi Christian Can I suggest a 'summary diff' option It's basically a diff between the tree of the commit and the tree of the parent commit It would show what files have changed rather than the diff of the files that have changed. (kinda like diffstat without the for now) (or maybe just