## Standard Subversion layout

Create a git clone of that includes your Subversion trunk, tags, and branches with

&lt;pre&gt;git svn clone http://svn.example.com/project -T trunk -b branches -t tags&lt;/pre&gt;

The `--stdlayout` option is a nice shortcut if your Subversion repository uses the typical structure:

&lt;pre&gt;git svn clone http://svn.example.com/project --stdlayout&lt;/pre&gt;

Make your git repository ignore everything the subversion repo does:

&lt;pre&gt;git svn show-ignore &gt;&gt; .git/info/exclude&lt;/pre&gt;

You should now be able to see all the Subversion branches on the git side:

&lt;pre&gt;git branch -r&lt;/pre&gt;

Say the name of the branch in Subversion is `waldo`. On the git side, you&#39;d run

&lt;pre&gt;git checkout -b waldo-svn remotes/waldo&lt;/pre&gt;

The -svn suffix is to avoid warnings of the form

&lt;pre&gt;warning: refname &#39;waldo&#39; is ambiguous.&lt;/pre&gt;

To update the git branch `waldo-svn`, run

&lt;pre&gt;git checkout waldo-svn
git svn rebase&lt;/pre&gt;


----------

## Starting from a trunk-only checkout

To add a Subversion branch to a trunk-only clone, modify your git repository&#39;s `.git/config` to contain

&lt;pre&gt;[svn-remote &quot;svn-mybranch&quot;]
        url = http://svn.example.com/project/branches/mybranch
        fetch = :refs/remotes/mybranch&lt;/pre&gt;

You&#39;ll need to develop the habit of running

&lt;pre&gt;git svn fetch --fetch-all&lt;/pre&gt;

to update all of what `git svn` thinks are separate remotes. At this point, you can create and track branches as above. For example, to create a git branch that corresponds to mybranch, run

&lt;pre&gt;git checkout -b mybranch-svn remotes/mybranch&lt;/pre&gt;

For the branches from which you intend to `git svn dcommit`, keep their histories linear!

----------

## Further information

You may also be interested in reading an [answer to a related question][1].

[1]: https://stackoverflow.com/questions/3140356/working-in-sync-with-svn-upstream/3220481#3220481

I have the following code:

    import matplotlib.pyplot as plt

    cdict = {
      &#39;red&#39;  :  ( (0.0, 0.25, .25), (0.02, .59, .59), (1., 1., 1.)),
      &#39;green&#39;:  ( (0.0, 0.0, 0.0), (0.02, .45, .45), (1., .97, .97)),
      &#39;blue&#39; :  ( (0.0, 1.0, 1.0), (0.02, .75, .75), (1., 0.45, 0.45))
    }
 
    cm = m.colors.LinearSegmentedColormap(&#39;my_colormap&#39;, cdict, 1024)
 
    plt.clf()
    plt.pcolor(X, Y, v, cmap=cm)
    plt.loglog()
    plt.xlabel(&#39;X Axis&#39;)
    plt.ylabel(&#39;Y Axis&#39;)
 
    plt.colorbar()
    plt.show()

So this produces a graph of the values &#39;v&#39; on the axes X vs Y, using the specified colormap. The X and Y axes are perfect, but the colormap spreads between the min and max of v. I would like to force the colormap to range between 0 and 1.

I thought of using:

    plt.axis(...)

To set the ranges of the axes, but this only takes arguments for the min and max of X and Y, not the colormap.

**Edit:**

For clarity, let&#39;s say I have one graph whose values range (0 ... 0.3), and another graph whose values (0.2 ... 0.8).

In both graphs, I will want the range of the colorbar to be (0 ... 1). In both graphs, I want this range of colour to be identical using the full range of cdict above (so 0.25 in both graphs will be the same colour). In the first graph, all colours between 0.3 and 1.0 won&#39;t feature in the graph, but will in the colourbar key at the side. In the other, all colours between 0 and 0.2, and between 0.8 and 1 will not feature in the graph, but will in the colourbar at the side.

Set Colorbar Range in matplotlib

I want to run &#39;make install&#39; so I have everything I need, but I&#39;d like it to install the things in their own folder as opposed to the system&#39;s /usr/bin etc. is that possible? even if it references tools in the /usr/bin etc.? 

Make install, but not to default directories?

I have checked out a svn repository using git svn. Now I need to checkout one of the branches and track it. Which is the best way to do it?

Checkout remote branch using git svn

<p>I have checked out a svn repository using git svn. Now I need to checkout one of the branches and track it. Which is the best way to do it?</p>


Somewhen (around the 1.6.x releases, I think) git became aware of changes inside submodules. That only serves to annoy me:


&lt;pre&gt;
$ git status vendor | grep modified:
#       modified:   vendor/rails (modified content)
&lt;/pre&gt;

&lt;pre&gt;
$ git diff vendor/
diff --git a/vendor/rails b/vendor/rails
--- a/vendor/rails
+++ b/vendor/rails
@@ -1 +1 @@
-Subproject commit 046c900df27994d454b7f906caa0e4226bb42b6f
+Subproject commit 046c900df27994d454b7f906caa0e4226bb42b6f-dirty
&lt;/pre&gt;

Please make it stop?

### Edit:

Ok, so I have an answer. Now I have another question:

Can I put this in `~/.gitconfig`? From my initial it appears that I cannot, and I didn&#39;t see anything promising by skimming the patch. (I guess I can still make an alias.)

Git: can I suppress listing of &#39;modified content&#39;/dirty submodule entries in status, diff, etc?

I have an existing git repo (a bare one) which has up to this point only been writable by me.  I want to open it up to some UNIX user group, foo, so that all members of foo can push to it.  I&#39;m aware that I can easily set up a *new* git repo with:

    git init --bare --shared=group repodir
    chgrp -R foo repodir

But I need the equivalent operation for an *existing* repo dir.

How to configure an existing git repo to be shared by a UNIX group

Which is efficient? SSH:// or Git://  (File compression)

I understand in Git, git protocol is smart because there is a protocol agent on both ends of communication to compress the file transfer resulting in faster clone by efficiently using the network bandwidth.

From [an O&#39;Reilly book][1] I found the following statements.

    For secure, authenticated connections, the Git native 
    protocol can be tunneled over an SSH connection using
    the following URL templates:

    ssh: //[user@]example.com[:port]/path/to/repo.git
    ssh: //[user@]example.com/path/to/repo.git
    ssh: //[user@]example.com/~user2/path/to/repo.git
    ssh: //[user@]example.com/~/path/to/repo.git*

I&#39;m not sure if the author means what he says. He talks of git protocol getting tunneled over SSH. 

From my perspective, unless you connect to the git port (agent port), the protocol is not in effect. And SSH is merely an uncompressed file transfer. But as per the author, if we use SSH he says the git protocol is tunneled over it. So is SSH smarter in GIT?

Von C,
Thanks for your answer. &quot;Network protocols (HTTP and Git) are generally read-only&quot; Git can be made `rw` when you run the daemon with `--enable=receive-pack`. 

Following are my concerns.  
When they say git protocol is smart, they mean when you execute `git clone`, Git server agent compresses the data that is sent back to the client, so the clone should be faster. In my use case I&#39;ll be setting the Git server in Hongkong and using it on San Jose and other countries as well, So I want to be efficient over network due to latency concerns.

So my question is when I use `git clone ssh://user@server/reposloc` do I get the benefits of git protocol also? As per O&#39;Reilly author book he means git is tunneled over ssh, then how does git protocol work when I don&#39;t have git daemon running on the server.

So using SSh://xyz... does it give both the benefit of ssh and git protocols?

Appreciate your answers in advance.


  [1]: https://books.google.com/books?id=ZkXELyQWf4UC&amp;lpg=PA201&amp;pg=PA201

Which is the smarter git protocol, ssh or git(over ssh) or https protocol?

How do I check whether the remote repository has changed and I need to pull?

Now I use this simple script:

    git pull --dry-run | grep -q -v &#39;Already up-to-date.&#39; &amp;&amp; changed=1

But it is rather heavy.

Is there a better way? The ideal solution would check all the remote branches, and return names of the changed branches and the number of new commits in each one.


Check if pull needed in Git

I think many developers like to investigate sources with the help of `git gui blame`. As explained in the [commit for Linux-2.6.12-rc2][2] (also [mirrored at Github][1]), it needs to have special historical Linux repository for this purpose.

&gt; ### Linux-2.6.12-rc2

&gt; Initial git repository build. I’m not bothering with the full history,
even though we have it. We can create a separate “historical” git
archive of that later if we want to, and in the meantime it’s about
3.2GB when imported into git — space that would just make the early
git days unnecessarily complicated, when we don’t have a lot of good
infrastructure for it.

&gt; Let it rip!

I have looked at a lot of the prepared historical repositories but I didn’t find one containing changes going back to version zero, so I gave up and am asking this question here.

[1]: https://github.com/torvalds/linux/commit/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
[2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2

Linux kernel &quot;historical&quot; git repository with full history

I have a &quot;fresh&quot; git-svn repo (11.13 GB) that has over a 100,000 objects in it.

I have preformed

    git fsck
    git gc

on the repo after the initial checkout.

I then tried to do a

    git status

The time it takes to do a git status is anywhere from 2m25.578s and 2m53.901s

I tested git status by issuing the command

    time git status

5 times and all of the times ran between the two times listed above.

I am doing this on a Mac OS X, locally not through a VM.

There is no way it should be taking this long.

Any ideas? Help?

Thanks.

**Edit**

I have a co-worker sitting right next to me with a comparable box.  Less RAM and running Debian with a jfs filesystem.  His **git status** runs in .3 on the same repo (it is also a git-svn checkout).

Also, I recently changed my file permissions (to 777) on this folder and it brought the time down considerably (why, I have no clue).  I can now get it done anywhere between 3 and 6 seconds.  This is manageable, but still a pain.

Git is really slow for 100,000 objects. Any fixes?

I want to take a function out of one file and put it into another, but keep the blame history.

    cp a.php b.php

    vim b.php
    # delete everything but 1 function

    vim a.php
    # delete the 1 function

    git add a.php b.php
    git commit

But if I run `git blame b.php` I only see it blaming to this new commit.

Keep git history when splitting a file

When doing a `git diff` it says *&quot;No newline at end of file&quot;*.

What&#39;s the significance of the message and what&#39;s it trying to tell us?

What&#39;s the significance of the &quot;No newline at end of file&quot; log?

We have recently migrated to Git from SVN. We have setup a bare repository on one machine in our LAN network and cloned on other machines. Now when anyone do the changes and commits we want that he sends the pull request to the bare repo (by telling or emailing or any other way) after that one will go through the changes and pull it on bare repository (same as it works on GitHub).

Do we need to install any interface or there is some commands in Git itself?


How to send pull request on Git

I know that I can use the `git diff` command to check the changes, but, as far as I understood, it is directory based. This means it gives all the changes of all files on the current directory.

_How can I check only the changes in one specific file?_ Say, I have changed files `file_1.rb`, `file_2.rb`, ..., `file_N.rb`, but I am only interested in the changes in the file `file_2.rb`. How do I check these changes then (before I commit)?

Content Type	Original Author	Original Content on Stackoverflow
Question	markovuksanovic	View Question on Stackoverflow
Solution 1 - Git	Greg Bacon	View Answer on Stackoverflow

Checkout remote branch using git svn

Git Problem Overview

Git Solutions

Solution 1 - Git

Standard Subversion layout

Starting from a trunk-only checkout

Further information

Make install, but not to default directories?

Set Colorbar Range in matplotlib

Attributions