From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] About Git through SSH
Date: Fri, 3 Sep 2010 09:37:29 -0500 [thread overview]
Message-ID: <201009030937.31967.minimod@morethan.org> (raw)
In-Reply-To: <20100903150459.059d682a@surf>
On Fri September 3 2010, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 3 Sep 2010 07:30:54 -0500
> "Michael S. Zick" <minimod@morethan.org> wrote:
>
> > Yup.
> > Please supply git version number(s).
>
> Just the normal Git from the latest Ubuntu, i.e:
>
> $ git --version
> git version 1.7.0.4
>
Ah, so, there is the difference - Apples and Oranges
I support users back to the oldest, commonly used, git versions -
Where I define that as the version in the current Debian stable release.
So the commentary in the gitolite release still applies to older git versions.
http://packages.debian.org/lenny/git-core
Somewhere between v1.5 and v1.7 they must have added parsing "ssh://" to the git client.
You might want to add a comment in the "Minimum Software Requirements" of Buildroot,
to go along with the addition of the user specified scheme feature for the case of
"git xxx ssh://..."
style URIs
Might cut down on the end-user puzzlement of: "Why doesn't this work for me?"
Note: I think the change happened at v1.6 but I haven't checked to be certain.
Mike
> > Any additional patches or local changes / customizations to your git
> > client?
>
> No, nothing. I think as soon as your user has write access to the remote
> location through SSH, git just works.
>
> However, as I said:
>
> > > As far as I see, Gitolite introduces per-branch or per-tag
> > > permissions, but plain Git already allows per-repository
> > > permissions. No ?
>
> Maybe that's what you're looking for and which is not supported by
> standard git.
>
> Regards,
>
> Thomas
next prev parent reply other threads:[~2010-09-03 14:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 10:09 [Buildroot] [RESEND/PATCH] Git/Svn downloaders Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 1/8] Remove the spider feature Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 2/8] Cleanup the VCS commands configuration Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 3/8] Update defconfigs with new VCS config options Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 4/8] Implement basic non-wget download methods Maxime Petazzoni
2010-09-02 12:37 ` Michael S. Zick
2010-09-02 12:50 ` Thomas Petazzoni
2010-09-03 12:30 ` Michael S. Zick
2010-09-03 13:04 ` [Buildroot] About Git through SSH Thomas Petazzoni
2010-09-03 14:37 ` Michael S. Zick [this message]
2010-09-03 15:03 ` Thomas Petazzoni
2010-09-03 15:59 ` Michael S. Zick
2010-09-04 1:25 ` Paul Jones
2010-09-04 16:58 ` Thomas Petazzoni
2010-09-05 1:50 ` Paul Jones
2010-09-05 3:05 ` James J. Dines
2010-09-05 3:12 ` James J. Dines
2010-09-02 10:09 ` [Buildroot] [PATCH 5/8] Use the normal download method for Tremor Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 6/8] Use the normal download method for libsvgtiny Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 7/8] Re-implement the source-check and external-deps targets Maxime Petazzoni
2010-09-02 10:19 ` [Buildroot] Missed a bug Maxime Petazzoni
2010-09-02 10:19 ` [Buildroot] [PATCH 7/8] Re-implement the source-check and external-deps targets Maxime Petazzoni
2010-09-02 10:24 ` Thomas Petazzoni
2010-09-02 10:31 ` Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 8/8] Revert "Makefile.package.in: allow packages to override download step" Maxime Petazzoni
2010-09-02 10:51 ` Thomas Petazzoni
2010-09-02 10:59 ` Maxime Petazzoni
2010-09-02 12:03 ` [Buildroot] [RESEND/PATCH] Git/Svn downloaders Thomas Petazzoni
2010-09-07 14:58 ` Maxime Petazzoni
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=201009030937.31967.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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