git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: first impressions to git

From
Petr Baudis <pasky@suse.cz>
Date
Sep 18, 2005, 14:54 UTC
Message-ID
<20050918145434.GA22391@pasky.or.cz>
In-Reply-To
<20050918111259.GA10882@schottelius.org>

Dear diary, on Sun, Sep 18, 2005 at 01:12:59PM CEST, I got a letter where Nico -telmich- Schottelius <nico-linux-git@schottelius.org> told me that...

> Hello!
Hello,
> My first impressions are:
> 
> - many commands, reminds me of arch/tla

this is one of Cogito's considerations, I try to keep the number of commands low. It's 26 non-admin commands now, which might raise a bit yet, but hopefully not by much. And I was thinking about coupling stuff like cg-branch-* to a single command.

> - I am not able to upload cinit, because
>    o adding directories with files and files I want to exclude is not easily
>      possible
Just fixed, cg-init should now DTRT.
>    o it's not clear to me, how I should publish (push)
>       - scp/rsync from outside
>       - git/cogito push

Push works fine for anything but the initial push - recursive scp or rsync of the whole repository is probably the easiest solution. It would be nice if git-send-pack would support the initial push.

>    o excluding *.o seems not to work, neither through .gitignore nor through
>      .git/info/exlude
It should now work during the initial commit.
> - How do I check integrity of files, is signed files somehow implemented?

This was discussed on IRC, it seems signed tags were the answer you were looking for.

> I've written some notes down in
>    http://creme.schottelius.org/~nico/temp/cogito
Pretty much all of this solved now, I think.
>    http://creme.schottelius.org/~nico/temp/git-erfahrungen
> 
> Adding directories with git-script-add (or whatever) would be nice in the way
> it adds the contents of the directory recursively.
cg-add -r implemented now.
>    o cogito could in fact be a nice frontend, after removing the current bugs
>      and if it has nicer error messaeges, which tell me WHAT I did wrong and
>      HOW to do it right.

This was one thing I kept in mind when making Cogito as well, I tried to make its error messages as helpful as possible. It would be great if you could point out where _Cogito_'s error messages might be more helpful (it's tougher with Git, but I'm sure they'll love to make their error messages more helpful as well - one thing I _really_ don't want to get into is filtering Git's error messages and rewriting them ;-).

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox
Previous: Nico -telmich- SchotteliusNext: Daniel Barkalow
Message 2 of 11 in “first impressions to git”
  1. Nico -telmich- SchotteliusSep 18, 2005
  2. Petr BaudisSep 18, 2005
  3. Daniel BarkalowSep 18, 2005
  4. Junio C HamanoSep 18, 2005
  5. Nico -telmich- SchotteliusSep 18, 2005
  6. Kay SieversSep 18, 2005
  7. Junio C HamanoSep 18, 2005
  8. Petr BaudisSep 18, 2005
  9. Junio C HamanoSep 18, 2005
  10. Linus TorvaldsSep 18, 2005
  11. Sven VerdoolaegeSep 19, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.