[git-users] احلي شات عربي

[mahmoud makhareta]

*احلي شات عربي*
*مجانا بكاميرات من
هنــا
*
*http://online-edu2all.blogspot.com/2012/07/e-learning-based-computer.html*

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] git contents model

[PJ Weisberg]

On Fri, Jul 13, 2012 at 5:38 AM, Angelo Borsotti
 wrote:
> Hi,
>
> I guess that a tarball would be the distro of the project, i.e. what is
> deployed,
> while a released project should contain the .git repo, with all the history
> in it
> so as to let future developers have all the data to start a new development.
> In such a case what is not needed are the files since they are also
> contained
> in the .git repo. I was wandering why there should instead be a need to have
> also the files (note that a directory with a .git in it and no other files
> is a
> project with a pending change in it that is the removal of all files, as
> reported
> by git status).

Ah, you're talking about a "bare" repository, with no working
directory.  That's actually the most common way to set up a repository
that's meant to be distribution point.  In fact, if the repository is
*not* bare, then by default you won't be able to push to the branch
that's checked out.

To create a bare repo, use 'git init --bare' or 'git clone --bare '.

To make an existing repo bare, use 'git config --bool core.bare true',
move the .git directory and give it a better name (i.e., 'mv .git
../my-project.git'), then you can delete the old working directory.

(Credit to 
http://stackoverflow.com/questions/2199897/git-convert-normal-to-bare-repository
for part of this answer.)

-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] "cannot spawn ssh" while trying to push changes to remote (e.g. github)

[Thomas Ferris Nicolaisen]

On Friday, July 13, 2012 1:48:06 PM UTC+2, Patryk Małek wrote:
>
> So to reproduce what I have done besides reinstalling a bunch of times: 
> - I have uninstalled Git and all its GUI frontends from the system that I 
> have installed (git extensions, github for windows etc ect)
> - I have deleted  *GIT_SSH * environmental variable 
> - uninstalled whole putty package
> - cleared git config files and keys etc
> - used ccleaner to clean registry and disk from unnecessary files , 
> registry keys
> - restarted Windows 7 (64 bit)
>
> THEN, I have downloaded newest version of git from website 
> https://github.com/downloads/msysgit/git/Git-1.7.11-preview20120620.exe 
> using settings to integrate git with command line.
>
> and while trying to do anything involving access through SSH i have 
> obtained once again 'Cannot spawn ssh' error message.
>
> I have no idea whatsoever what can be done more in this matter. I have 
> even used processmonitor application to take a look what/how git is trying 
> to launch ssh client but I have not found it there
>

OK, so you have a clean slate and you want to do the OpenSSH approach in a 
normal Windows command line (cmd.exe). 

During the Git installer, I assume you chose "Run Git and included Unix 
tools from the Windows Command Prompt". This is the third and last option 
with the scary red warning below. *Did you choose this option? *If you did 
not choose this option, you have to use Git Bash instead of normal 
command-line below.

To make things a bit less complex, let's make sure SSH works. Try the 
following:

   - Start Command line (Start -> Run -> 'cmd')
   - ssh -T username@your-git-server

What does the command above output?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/n0PdptAdIT4J.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] git contents model

[Angelo Borsotti]

Hi,

I guess that a tarball would be the distro of the project, i.e. what is
deployed,
while a released project should contain the .git repo, with all the history
in it
so as to let future developers have all the data to start a new development.
In such a case what is not needed are the files since they are also
contained
in the .git repo. I was wandering why there should instead be a need to have
also the files (note that a directory with a .git in it and no other files
is a
project with a pending change in it that is the removal of all files, as
reported
by git status).

-Angelo

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] git contents model

[PJ Weisberg]

On Friday, July 13, 2012, Angelo Borsotti  wrote:
> in the work directory AND in the .git. At this point if I delete the
files from the work directory, I take
> the project to an inconsistent state (as reported by git status, which
tells me that all files have been
> removed). So, the "nornal" state of a released project is to have its
files stored twice.

That's the "normal" state of a work directory in which no work has been
done yet.  The "normal" state of a released project would be a tarball, war
file, or something else with no .git directory at all.

-- 
-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] "cannot spawn ssh" while trying to push changes to remote (e.g. github)

[Patryk Małek]

So to reproduce what I have done besides reinstalling a bunch of times:
- I have uninstalled Git and all its GUI frontends from the system that I
have installed (git extensions, github for windows etc ect)
- I have deleted  *GIT_SSH * environmental variable
- uninstalled whole putty package
- cleared git config files and keys etc
- used ccleaner to clean registry and disk from unnecessary files ,
registry keys
- restarted Windows 7 (64 bit)

THEN, I have downloaded newest version of git from website
https://github.com/downloads/msysgit/git/Git-1.7.11-preview20120620.exe
using settings to integrate git with command line.

and while trying to do anything involving access through SSH i have
obtained once again 'Cannot spawn ssh' error message.

I have no idea whatsoever what can be done more in this matter. I have even
used processmonitor application to take a look what/how git is trying to
launch ssh client but I have not found it there


2012/7/11 Thomas Ferris Nicolaisen 

> On Tuesday, July 10, 2012 11:23:46 PM UTC+2, Patryk Małek wrote:
>>
>> Hello again,
>>
>> A lot of time passed since my last e-mail but I have been trying some
>> different approaches to this problem but ... none worked. I have tried as
>> you suggested to go with *Github for Windows* which actually worked -
>> but it's not a go for me since I need this now for my work project where we
>> have a Git repo on our own server.
>>
>> All the rest of the options have failed for me. I Have tried setting the
>> *GIT_SSH * to both *C:\Putty\plink.exe*  or leaving it as it was after
>> the install with *openssh*'s path(+exe name) but none worked - I still
>> get *"cannot spawn"* error.
>>
>> I have also tried
>> http://blog.tfnico.com/2012/04/my-git-setup-on-windows.html  and
>> https://help.github.com/articles/set-up-git#platform-windows  but still
>> the same.
>>
>> I have reinstalled Git at least 50 times already trying different
>> options, clearing it's environmental variables and directories at the same
>> time.
>>
>> Why is this not working for me ?!
>>
>
>
> Github for Windows bundles msysgit and openssh, so if it works there it
> means there's still a configuration error on your side.
>
> Note that you can point Github for Windows towards other non-Github
> repositories. You can also use the command line Git that bundles with
> Github for Windows. If this works for you, I don't see what the problem is.
>
> Anyhow, if you want concrete suggestions, you have to give us some
> concrete description of your environment, the steps you made and the error
> messages you got. Saying "I tried 50 times" is not helping.
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/git-users/-/ANk9rHnI-gYJ.
>
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>



-- 

pozdrawiam
Patryk Małek

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

[git-users] Re: git status long time, gitignore

[jack sparrow]

On Wednesday, July 11, 2012 11:35:11 AM UTC+5:30, Thomas Ferris Nicolaisen 
wrote:
>
> ok still no luck, i've cloned the tree to my local hard disk running 
>> ubuntu in vmplayer on windows. 
>> i see the performance has become worse, now git status it is taking 
>> more than 
>> two minutes. this is a little disappointment. does running from vm has 
>> any drawbacks ? 
>>
>
> There is an overhead in running on a VM, yes. I would have guessed it was 
> negligible, but I might be wrong. 
>
> It also depends what partition or filesystem the Git repository is located 
> on. Here's somebody with a similar 
> setupand
>  the Git repository in a "shared folder", which is also slow.
>
> Can you tell us the absolute path of your Git repository on the Ubuntu 
> image, along with the output of running '*mount*' and '*df*'?
>

git# 
git# pwd
/home/sinbad/repo/hm
git#
git# df .
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sdb1 20125340   7230704  11872328  38% /
git#
git# df
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sdb1 20125340   7230700  11872332  38% /
none247388   624246764   1% /dev
none254000   224253776   1% /dev/shm
none254000   104253896   1% /var/run
none254000 0254000   0% /var/lock
.host:/  244196348 233827328  10369020  96% /mnt/hgfs
git#
git# mount
/dev/sdb1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,noexec,nosuid,nodev)
.host:/ on /mnt/hgfs type vmhgfs (rw,ttl=1)
none on /proc/fs/vmblock/mountPoint type vmblock (rw)
gvfs-fuse-daemon on /home/sinbad/.gvfs type fuse.gvfs-fuse-daemon 
(rw,nosuid,nodev,user=sinbad)
 

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/iiODzMGs9vUJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

[git-users] git contents model

[Angelo Borsotti]

I have the impression that the underlying model of a git repository is made 
of a .git archive plus a work
directory in which (some version of, e.g. the latest) the files are 
present. I.e. at least one version of
the files are stored twice.
E.g. suppose I create a new project and initialize git in it. Then I can 
create files and commit changes.
When I am done, i.e. the files are ready to be released, I make the last 
commit, and thenI have the files
in the work directory AND in the .git. At this point if I delete the files 
from the work directory, I take
the project to an inconsistent state (as reported by git status, which 
tells me that all files have been
removed). So, the "nornal" state of a released project is to have its files 
stored twice.
Is this correct?
Is this what we want?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/sGf0sgwK_NwJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

[git-users] Re: Error on repository clone: select: Not enough memory ... index-pack failed

[Tudor]

I am having the same problem.
I tried everything, modified all configs from git but still with error. 
I also tried to make another repository with size greater than 210 MiB and 
it's still with the same problem.
>From one unix to another both repositories works like charm. I tested and 
it is not a time-based problem.
It seems that git for windows has a problem with transfers larger than 200 
MiB (clone, push, pull, etc) with this out of memory leak.
Please help ! 

Thank you in advance,
Tudor Vasinca


On Wednesday, July 11, 2012 10:28:19 AM UTC+3, Sergiu wrote:
>
> Hi.
>  
> I've been struggling for few days now with this, so I was hoping I could 
> get some suggestions here.
> It's about cloning a repo. It used to work, but it just started to throw 
> this error when I "git clone ssh://git@hostname:10101/test.git":
>
> remote: Counting objects: 11401, done.
> remote: Compressing objects: 100% (9278/9278), done.
> select: Not enough memory4561/11401), 206.60 MiB | 1.01 MiB/s
> fatal: The remote end hung up unexpectedly
> fatal: early EOF
> fatal: index-pack failed
>
> I cannot clone this repo anymore. It always dies around 206-208 MiB. 
> Anyone dealt with this before? Any suggestions? Thank you.
>
> # Server: CentOS release 6.2 (Final) 2.6.32-220.el6.x86_64
> # cat /proc/meminfo
> # MemTotal:   16316936 kB (16 316 936 kilobytes = 15.5610428 gigabytes)
> # MemFree: 5251088 kB (5 251 088 kilobytes = 5.00782776 gigabytes)
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/nW08VxduCDcJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.