From: Jakub Narebski <jnareb@gmail.com>
To: m.arya@yahoo.com
Cc: git@vger.kernel.org
Subject: Re: Few Questions
Date: Tue, 20 Jan 2009 07:44:27 -0800 (PST) [thread overview]
Message-ID: <m3r62yx9qi.fsf@localhost.localdomain> (raw)
In-Reply-To: <726600.29783.qm@web35708.mail.mud.yahoo.com>
"Arya, Manish Kumar" <m.arya@yahoo.com> writes:
> Hi,
>
> I am new to Git. Earlier I have configured svn with LDAP auth and
> svnwebclient.
>
> I want to have following with Git
>
> - LDAP and ssh authentication.
>
Instead of inventing (and failing) its own protocol and its own
authentication git uses established solutions for authentication: SSH
for "smart" server, and WebDAV for push via (currently only "dumb")
HTTPS protocol.
There exist solutions that help with setting up SSH for git:
git-shell, ssh_acl, and I think most commonly used Gitosis (see
seminal reference about Gitosis on http://git.or.cz/gitwiki/BlogPosts).
> - checkin and checkout using web interface and ssh
>
Git is distributed version control system: checkin (named 'commit' in
git) and checkout are _local_ operations. Fetch (getting new changes
from remote repository) and clone (creating new local repository
following or forking specified remote repository) can be done via
local filesystem, via git:// protocol, via "dumb" HTTP, and via SSH.
Push (sending changes to remote repository) needs autheticated
channel: most common used is SSH, but you can also use WebDAV with
HTTPS.
There are web interfaces for Git, something like SVN::Web or ViewVC,
like gitweb (in Perl, developed in git.git repository) and cgit (in C).
See also "Web interfaces" section on InterfacesFrontendsAndTools page
on git wiki.
> - when ever someone checkin something then a email should be send to
> a email address (a mailing list)
If by 'checkin' you mean publishing changes to a server (i.e. push in
git terminology), see for example contrib/hooks/post-receive-email
hook.
> please let me know how to do this with Git
Please learn that Git is _different_ from Subversion, and not try to
follow your SVN workflow and expectations blindly.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-01-20 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 10:38 Few Questions Arya, Manish Kumar
2009-01-20 11:04 ` Matthieu Moy
2009-01-20 15:44 ` Jakub Narebski [this message]
2009-01-20 16:04 ` Shawn O. Pearce
2009-01-21 11:08 ` R. Tyler Ballance
-- strict thread matches above, loose matches on Subject: below --
2007-12-08 0:11 Few questions Michael Makuch
2007-12-08 3:17 ` Guy Watkins
2007-12-08 12:03 ` David Greaves
2007-12-09 4:17 ` Michael Makuch
2007-12-08 3:22 ` Corey Hickey
2006-04-26 8:04 Miroslav Vasic
2006-04-26 8:32 ` Dominik Brodowski
2006-04-27 9:16 ` Miroslav Vasic
2006-04-27 9:29 ` Dominik Brodowski
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=m3r62yx9qi.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=m.arya@yahoo.com \
/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.