[git-users] git name-rev --tags ouput

2013-08-01 Thread dexter ietf
what's the meaning of the following in git name-rev  output.
i know the commit went into 100.15 version, but what to make
of ^2~4^2~1, any pointer to documentation ?

tags/100.15^2~4^2~1

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [git-users] git on nfs is outrageously slow

2013-08-01 Thread dexter ietf
On Wednesday, July 31, 2013 5:36:41 PM UTC+5:30, John McKown wrote:

> That's exactly what I do. I have my bare repository on an NFS mounted 
> filesystem, but my working directory on my local disk. It works well for me.
>
> Also, what is the speed between the local machine and the NFS server? I 
> have a gigabyte connection on a LAN. Also, how busy is the NFS server? What 
> else is running on the same server? How many concurrent users are there and 
> what are they doing? As you may have guessed, I am wondering if the problem 
> is the server or the connection to the server, rather than git itself.
>
> On Wed, Jul 31, 2013 at 6:39 AM, Johannes Müller 
> 
> > wrote:
>
>> You can make a local clone of your git repository and use the nfs git
>> repository to push your changes to. This way you get to work with git
>> with normal speed and only when pushing, there is a speed penalty.
>> Otherwise, you could try to configurate nfs so that it caches access to
>> the file. Note that afaik nfs might cause problems when you access the
>> same file simultaneously with several users because it does not support
>> locking a file.
>>
>> Johannes
>>
>> On 31.07.2013 13:01, dexter ietf wrote:
>> > please help on fixing it, it is so slow that i started hating git (for
>> > wrong reasons)
>> > i'm sure there is a way out, please help me to make my git faster.
>> >
>> > -dexter
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Git for human beings" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to git-users+...@googlegroups.com .
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to git-users+...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
the nfs server is from my company, cloning the tree to a local disk is good 
idea,
but i'd loose the backup functionality that nfs provides, and the build 
environment
is present in the nfs server as well, i'm not sure how can i get around 
this, or can
i clone the tree from my nfs tree. will the following scheme work ? are 
there any
documentation to do the same.


origin/master 
|
|
nfs server --- clone a tree here. t1 -- (build here)
|
|
local disk --- clone from t1, (work here, push to t1)

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [git-users] Workflow from personal to local to remote?

2013-08-01 Thread Magnus Therning
On Wed, Jul 31, 2013 at 08:22:10AM -0700, leam hall wrote:
> I'm trying to design a workflow for our team and could use some advice. My 
> git-fu is young. 
> 
> We have  a remote repo that will store the authoritative code. That will be 
> pulled to a server local repo where the team has access. Each person will 
> clone the local repo into their home directory, edit files, and then push 
> to the local repo. Somehow we will trigger code review and acks, and then 
> someone will push from the local repo to the authoritative repo. 
> 
> What I need help understanding is:
> 
> 1. How to prevent code being pushed from local repo to authoritative
>until it is reviewed? Is this a process issue or does git have a
>way to enforce it?

It is a process issue external to git, but I think this particular use
case is exactly what [gerrit][1] addresses.

/M

[1]: https://code.google.com/p/gerrit/

-- 
Magnus Therning  OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus


Perl is another example of filling a tiny, short-term need, and then
being a real problem in the longer term.
 -- Alan Kay


pgp77Nvcw3HQT.pgp
Description: PGP signature


[git-users] setup git server/web with lighttpd: gives …git-upload-pack not found

2013-08-01 Thread Jeanluca
I've setup lighttpd and gitweb. Created an empty repository as follows:

$server> git --version
git version 1.7.11.7
$server> git --bare init p1
$server> cd p1
$server> git update-server-info
$server> cd ..
$server> chown -R lighttpd:lighttpd p1

In the browser I can browse this repository, but when I try to clone it 
from the command line I get:

$> git clone https://example.com/git/project.git p1
Cloning into 'p1'...
fatal: 
https://example.com/git/project.git/info/refs?service=git-upload-pack not 
found: did you run git update-server-info on the server?

And, maybe it helps, here is my lighttpd configuration

alias.url += (
  "/static/gitweb.css"  => "/var/www/git/static/gitweb.css",
  "/static/git-logo.png"=> "/var/www/git/static/git-logo.png",
  "/static/git-favicon.png" => "/var/www/git/static/git-favicon.png",
  "/static/gitweb.js"   => "/var/www/git/static/gitweb.js",
  "/git"=> "/var/www/git/gitweb.cgi"
)

I did run 'git update-server-info', without success!
Any suggestions ?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.