On Monday, December 3, 2012 8:02:26 AM UTC+1, ARSHAD ALI wrote:
> Thank u sir, its mean i cannot push a single file after "commit" but whole
> working directory will be push to bare repository. I mean GIT works with
> directories not with single files in terms of push, pull, clone etc."AM I
> R
Hello,
I have run some bare repos with http & https on Apache and get this errors:
"GET /git/Simulation.git/info/refs?service=git-upload-pack HTTP/1.1" 200
2878 "-" "git/1.8.0"
"POST /git/Simulation.git/git-upload-pack
On Wed, 28 Nov 2012 16:36:37 -0800 (PST)
kumar wrote:
> I have a 20 GB project and when i try to push it into remote git
> using http i fails. I get the following error
[...]
> I even tried git config http.postBuffer 524288000 and it did not help.
>
> as an alternative i copied the project to th
I've been reading "Version Control using git" (already finish Pro Git). One
thing the author said was that git really encourages developers to commit
frequently. Mainly because they have an entire (at the time) copy of the
repository. So there's not a lot of overhead of sending files across the
I think what you're looking for is a squash merge. If you develop the
change in a dedicated feature branch like you describe, you can
transfer all of the changes to the master branch with the `--squash`
flag as follows:
git checkout master
git merge --squash some-feature
This concatenates all of
Thanks. I either didn't see that in the books, or was asleep. I'll read up
on it.
On Dec 3, 2012 7:07 PM, "Ryan Hodson" wrote:
> I think what you're looking for is a squash merge. If you develop the
> change in a dedicated feature branch like you describe, you can
> transfer all of the changes t
There's also the option of cleaning up your commits using interactive
rebase (git rebase -i, google for some examples, it's very neat).
Then there is the question of whether you actually want to have a
merge-commit as a "sign-off" for the completed feature, and keep the
smaller work-commits (al
Technically, Git has no maximum limit on repository size. In reality, a 20
GB repo is probably way too large. You'd be better off breaking it up into
separate repositories. It might also be worth just doing a sanity check on
the contents of the repository. I've worked on some very large projects
(t
I found this answer to work quite well so far, for my limited testing.
http://cygwin.com/ml/cygwin/2007-09/msg00584.html.
Basically text mounts mess everything up. Git will work on binary mounts of
cygwin.
On Saturday, December 1, 2012 2:49:40 PM UTC-8, munene kiruja wrote:
>
> Git already ca
Thank you all for your replies.
On Saturday, December 1, 2012 2:49:40 PM UTC-8, munene kiruja wrote:
>
> Git already came in with the cygwin install. So I thought I could just
> start using it. After 2 days of reading and searching, not even one step
> ahead. Anyone help. What am I doing wrong?
10 matches
Mail list logo
