From: Petr Baudis <pasky@suse.cz>
To: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Cc: git@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Christian Gierke <ch@gierke.de>
Subject: Re: first impressions to git
Date: Sun, 18 Sep 2005 16:54:34 +0200 [thread overview]
Message-ID: <20050918145434.GA22391@pasky.or.cz> (raw)
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
next prev parent reply other threads:[~2005-09-18 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 11:12 first impressions to git Nico -telmich- Schottelius
2005-09-18 14:54 ` Petr Baudis [this message]
[not found] ` <94fc236b050918073351075bb4@mail.gmail.com>
2005-09-18 21:18 ` Nico -telmich- Schottelius
2005-09-18 21:39 ` Kay Sievers
2005-09-18 22:09 ` Junio C Hamano
2005-09-18 22:11 ` Petr Baudis
2005-09-18 22:23 ` Junio C Hamano
2005-09-18 22:29 ` Linus Torvalds
2005-09-18 16:56 ` Daniel Barkalow
2005-09-18 17:31 ` Junio C Hamano
2005-09-19 19:14 ` Sven Verdoolaege
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=20050918145434.GA22391@pasky.or.cz \
--to=pasky@suse.cz \
--cc=ch@gierke.de \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=nico-linux-git@schottelius.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).