Regards, Kieran.
(Sent from my iPhone)
On Apr 6, 2012, at 5:31 PM, Daniel Beatty wrote:
> Greetings Kieran,
> Well this Gitolite sounds like an excellent tool.
It is. If I can fit it in I will cover gitolite at WOWODC since it is free and
available to all.
> Although, there are employer
Greetings Kieran,
Well this Gitolite sounds like an excellent tool. Although, there are
employers that have paranoia for a good reason. Some have been burned, others
are paid to have this paranoia, and others just simply work some national
government. Whatever the excuse is, there seems to be
Am 05.04.2012 um 21:35 schrieb Pascal Robert:
> Yup, gitolite is your friend.
Another alternative working really well is gitosis [1].
[1] https://github.com/tv42/gitosis
>
>> Ricardo
>>
>> I have setup my own (or I should say Pascal did) git repository on my own
>> server. Works really we
Gitolite makes it easy to administer many repositories with less effort that
just basic setup for a single repo. Also allows a basic level of control over
what users can and cannot do on specific repositories.
Regards, Kieran.
(Sent from my iPhone)
On Apr 5, 2012, at 5:50 PM, Ted Archibald w
On Apr 5, 2012, at 2:38 PM, "Ricardo J. Parada" wrote:
>
>
> Basic / typical commands for forking wonder, cloning it, contributing back.
> ;-)
>
> How about the equivalent of svn:externals to integrate Wonder into our
> employer's git repository... Or maybe the command for checking out a
Gitolite users are "virtual" users and virtual permissions, so no need to give
them SSH access to the box.
> What's the advantage gitolite offers? I was reading up on it and I didn't
> get. What's the difference between a git server VS a computer just running
> git with ssh keys?
>
> On Thu,
What's the advantage gitolite offers? I was reading up on it and I didn't
get. What's the difference between a git server VS a computer just running
git with ssh keys?
On Thu, Apr 5, 2012 at 1:40 PM, Pascal Robert wrote:
> I would add:
>
> stashes : damn useful to try options without committi
I would add:
stashes : damn useful to try options without committing it. You can stash
your tests, try something else, stash that something else, and get back to the
first stash if you didn't like your work on the second stash.
post commit hooks (never tried those except in a GitHub context
Yup, gitolite is your friend.
> Ricardo
>
> I have setup my own (or I should say Pascal did) git repository on my own
> server. Works really well.
>
> --
> Paul Yu
> Sent with Sparrow
>
> On Thursday, April 5, 2012 at 3:19 PM, Ricardo J. Parada wrote:
>
>>
>>
>> Basic / typical commands f
Ricardo
I have setup my own (or I should say Pascal did) git repository on my own
server. Works really well.
--
Paul Yu
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, April 5, 2012 at 3:19 PM, Ricardo J. Parada wrote:
>
>
> Basic / typical commands for forking wonde
Basic / typical commands for forking wonder, cloning it, contributing back. ;-)
How about the equivalent of svn:externals to integrate Wonder into our
employer's git repository... Or maybe the command for checking out a
particular version of Wonder in time for building our apps and qa agains
Since I just switched over, I'd be curious to know which is better:
multiple large repositories with many projects (ala Wonder) or an
individual repository for each project. When I converted over from svn I
went with the former than the latter, and it seems fine.
Different workflows, what you do
Best practices for setting up repositories. One project per? All projects in
one?
Dealing with forks and making pull requests to Wonder
Jenkins :-)
Sent from my iPad
On 2012-04-03, at 3:39 PM, Kieran Kelleher wrote:
> Following Chuck's lead what would you like to get out of the "Usin
Following Chuck's lead what would you like to get out of the "Using
Git" session . what are the problems you are facing in the git world? I
have already done an outline of my session content, but would definitely try to
accommodate any requests also.
Feel free to respond to this em
14 matches
Mail list logo
