[pgrouting-dev] git newbie question

[Daniel Kastl]

Hi Steve,

If it's about the compile artifacts, then you could add this .gitignore
file:
https://github.com/pgRouting/pgrouting/blob/master/.gitignore

Kishore actually added it some time ago and it's also on the master branch.
But maybe it didn't make it everywhere yet.

Otherwise, you could just clone the repository twice in two directories.
And if you don't want all branches, maybe this helps:
http://strk.keybit.net/blog/tag/qgis/

Daniel


On Sun, Jul 10, 2011 at 8:20 AM, Stephen Woodbridge <woodbri at swoodbridge.com
> wrote:

> On 7/9/2011 5:40 PM, Daniel Kastl wrote:
>
>> Hi Steve,
>>
>> I actually never create directories, just switch branches with
>> "checkout" command.
>> The only issue there: it will prevent you from switching branches, when
>> you made some changes to the source and didn't commit first.
>>
>> Is there any particular reason to keep them in separate directories?
>>
>
> Yes for just this reason. I often compile in the source tree which leaves
> artifacts and sometimes play with the code but stuff would never get
> committed like debug stuff.
>
> -Steve
>
>  Daniel
>>
>>
>> On Sun, Jul 10, 2011 at 4:07 AM, Stephen Woodbridge
>> <woodbri at swoodbridge.com <mailto:woodbri at swoodbridge.**com<woodbri at swoodbridge.com>>>
>> wrote:
>>
>>    Jay,
>>
>>    Thanks. OK, that is interesting - it checks out the additional branch
>>
>>
>>    woodbri at mappy:~/work/ pgrouting-git/pgrouting$ git branch
>>    * gsoc-tdsp
>>      master
>>
>>    and converts the cwd to that branch.  And I can switch the directory
>>    between master and gsoc-tdsp with commands:
>>
>>    git checkout master
>>    git checkout gsoc-tdsp
>>
>>    respectively. So this is close, but it does not look like it is easy
>>    to create two directories one with each branch instantiated in it. I
>>    suppose I could rsync the checked out view into another directory or
>>    clone the repository for each separate instance I want and then
>>    change the instance to the branch.
>>
>>    The rsync method seems to work but is a little awkward. Well if
>>    anyone has any additional ideas, let me know.
>>
>>    -Steve
>>
>>
>>    On 7/9/2011 2:11 PM, Jay Mahadeokar wrote:
>>
>>        Hi,
>>
>>        Firstly, I am also a newbie in git and I have only learned
>>        commands that
>>        I are utterly essential for me. But I guess this could work.
>>
>>        |git checkout -b gsoc-tdsp origin/gsoc-tdsp
>>        |
>>
>>        Please refer [1] to be perfectly sure and also other options.
>>
>>        [1] http://progit.org/book/ch3-5. html
>>        <http://progit.org/book/ch3-5.**html<http://progit.org/book/ch3-5.html>
>> >
>>
>>        On Sat, Jul 9, 2011 at 11:27 PM, Stephen Woodbridge
>>        <woodbri at swoodbridge.com <mailto:woodbri at swoodbridge.**com<woodbri at swoodbridge.com>
>> >
>>        <mailto:woodbri at swoodbridge. com
>>
>>        <mailto:woodbri at swoodbridge.**com <woodbri at swoodbridge.com>>>>
>> wrote:
>>
>>            Hi all,
>>
>>            I have a git newbie question. I have checked out the git
>>        repository:
>>
>>            woodbri at mappy:~/work/ pgrouting-git/pgrouting$ git branch -r
>>              origin/HEAD
>>              origin/darp
>>              origin/debian
>>              origin/debian-karmic
>>              origin/debian-maverick
>>              origin/debian-natty
>>              origin/devel-2_0
>>              origin/gsoc-multimodal
>>              origin/gsoc-tdsp
>>              origin/master
>>              origin/pristine-tar
>>              origin/snapshot
>>              origin/snapshot-maverick
>>              origin/unittests
>>              origin/upstream
>>            woodbri at mappy:~/work/ pgrouting-git/pgrouting$ git tag -l
>>            debian/1.04-ppa12_lucid1
>>            debian/1.05-1_karmic1
>>            debian/1.05-1_lucid1
>>            debian/1.05-1_maverick1
>>            upstream/1.04
>>            upstream/1.05
>>            v1.05
>>
>>
>>            what I would like to do is create a directory for the
>>            gsoc-multimodal and gsoc-tdsp projects in say ../gsoc-tdsp and
>>            ../gsoc-multimodal and I can not figure out how to do this.
>>
>>            ~/work/pgrouting-git/pgrouting  is currently master
>>
>>            and I would like to create these:
>>
>>            ~/work/pgrouting-git/gsoc-tdsp
>>            ~/work/pgrouting-git/gsoc- multimodal
>>
>>            I'm sure there has to be a simple way to do this, but I'm
>>        not seeing it.
>>
>>            Thanks,
>>              -Steve
>>            ______________________________ _________________
>>            pgrouting-dev mailing list
>>        pgrouting-dev at lists.osgeo.org
>>        <mailto:pgrouting-dev at lists.**osgeo.org<pgrouting-dev at lists.osgeo.org>
>> >
>>        <mailto:pgrouting-dev at lists. osgeo.org
>>        <mailto:pgrouting-dev at lists.**osgeo.org<pgrouting-dev at lists.osgeo.org>
>> >>
>>
>>        http://lists.osgeo.org/ mailman/listinfo/pgrouting-dev
>>        <http://lists.osgeo.org/ mailman/listinfo/pgrouting-dev
>>        <http://lists.osgeo.org/**mailman/listinfo/pgrouting-dev<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
>> **> >
>>
>>
>>
>>
>>        --
>>        Regards,
>>        -Jay Mahadeokar
>>
>>  ______________________________**_________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/pgrouting-dev<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
>



-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20110710/1fc1f97c/attachment.html