From: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
To: git@vger.kernel.org
Cc: Kay Sievers <kay.sievers@vrfy.org>, Christian Gierke <ch@gierke.de>
Subject: first impressions to git
Date: Sun, 18 Sep 2005 13:12:59 +0200 [thread overview]
Message-ID: <20050918111259.GA10882@schottelius.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
Hello!
I was testing git for my needs with the following ideas in my mind:
- it must be easy to use
- documentation must be easy to find, understand and remember
- it should be fast
- optionally using the filesystem as a database would be nice
My first impressions are:
- many commands, reminds me of arch/tla
- nice idea with .git
- uses the filesystem
- using git directly seems to be more work than necessary
- cogito looks like a good frontend, but has some drawbacks
- it's not clear which protocols for pull/push are supported
- the documentation is not in sync with the programm (0.99.5 vs. 0.99.6)
- gitweb.cgi could be better documentated and supported
recursive directories when using $projects_list = $projectroot;
and splitting configuration completly outside of gitweb.cgi would be nice
(having .gitweb in the same directory as gitweb.cgi for instance)
- I am not able to upload cinit, because
o adding directories with files and files I want to exclude is not easily
possible
o it's not clear to me, how I should publish (push)
- scp/rsync from outside
- git/cogito push
o excluding *.o seems not to work, neither through .gitignore nor through
.git/info/exlude
- How do I check integrity of files, is signed files somehow implemented?
I've written some notes down in
http://creme.schottelius.org/~nico/temp/cogito
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.
That's it for the first impression, I would be happy for any hints and critic
if I did something 'really wrong' with git/cogito.
My current position to git/cogito is that using could be possible, but not
as comfortable (from a developers view) as it is with monotone.
Sincerly,
Nico
P.S.: These are mostly the negative things, I've to say that
o gitweb.cgi looks very beautiful
o git es very fast
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.
--
Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
Open Source nutures open minds and free, creative developers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2005-09-18 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 11:12 Nico -telmich- Schottelius [this message]
2005-09-18 14:54 ` first impressions to git Petr Baudis
[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=20050918111259.GA10882@schottelius.org \
--to=nico-linux-git@schottelius.org \
--cc=ch@gierke.de \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.