You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Andreas Pieber <an...@gmail.com> on 2010/12/12 14:54:06 UTC

git svn

Hey guys,

I'm not sure how you feel about git-svn but, for non-commiters they work quite
great (I can use and share a running version of karaf for my projects till
waiting for my patches to get into the trunk/branches). BUT instead of svn properties
git uses .gitignore for ignoring autogenerated files. These can be created, based 
on the svn ignores,  quite easy by using "git svn create-ignore" (but are also
marked as chagned themselves then :( ).

How do you feel about including these .gitignore files into the trunk/branches?
They wont hurt svn only devs, but help git-svn user, since the changes did not
become obfuscated by autogenerated files (or the autogenerated .gitignore
files).

WDYT?

kind regards,
andreas

Re: git svn

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
No problem Andreas :)

I don't use eclipse, but I'm gonna add the eclipse related folders in 
the gitignore.

Regards
JB

On 12/12/2010 09:12 PM, Andreas Pieber wrote:
> sry, get confused... typically I use git svn create-ignores for
> not-only-git-projects. This syncs svn:ignore with one .gitignore file per folder
> where svn:ignore is applied; because of the missing eclipse-classes entry (mvn
> eclipse:eclipse) I've used git svn create-ignore and suddenly have 20 new
> .gitignore files :)
>
> Sry for the confusion, but still: "eclipse-classes" is missing in the .gitignore file
>
> thanks and kind regards,
> andreas
>
> On Sun, Dec 12, 2010 at 06:25:18PM +0100, Jean-Baptiste Onofré wrote:
>> Hi Andreas,
>>
>> at least Guillaume and I use git.
>>
>> We already commited and updated a .gitignore file containing:
>>
>> *.i??
>> .project
>> .classpath
>> .settings
>>
>> I'm gonna add target.
>>
>> The same .gitignore file is present into the 2.1.x branch.
>>
>> So I think all is already there. I'm agree to add a svnignore file.
>>
>> Regards
>> JB
>>
>> On 12/12/2010 02:54 PM, Andreas Pieber wrote:
>>> Hey guys,
>>>
>>> I'm not sure how you feel about git-svn but, for non-commiters they work quite
>>> great (I can use and share a running version of karaf for my projects till
>>> waiting for my patches to get into the trunk/branches). BUT instead of svn properties
>>> git uses .gitignore for ignoring autogenerated files. These can be created, based
>>> on the svn ignores,  quite easy by using "git svn create-ignore" (but are also
>>> marked as chagned themselves then :( ).
>>>
>>> How do you feel about including these .gitignore files into the trunk/branches?
>>> They wont hurt svn only devs, but help git-svn user, since the changes did not
>>> become obfuscated by autogenerated files (or the autogenerated .gitignore
>>> files).
>>>
>>> WDYT?
>>>
>>> kind regards,
>>> andreas
>>>

Re: git svn

Posted by Andreas Pieber <an...@gmail.com>.
sry, get confused... typically I use git svn create-ignores for
not-only-git-projects. This syncs svn:ignore with one .gitignore file per folder
where svn:ignore is applied; because of the missing eclipse-classes entry (mvn
eclipse:eclipse) I've used git svn create-ignore and suddenly have 20 new
.gitignore files :) 

Sry for the confusion, but still: "eclipse-classes" is missing in the .gitignore file

thanks and kind regards,
andreas

On Sun, Dec 12, 2010 at 06:25:18PM +0100, Jean-Baptiste Onofré wrote:
> Hi Andreas,
> 
> at least Guillaume and I use git.
> 
> We already commited and updated a .gitignore file containing:
> 
> *.i??
> .project
> .classpath
> .settings
> 
> I'm gonna add target.
> 
> The same .gitignore file is present into the 2.1.x branch.
> 
> So I think all is already there. I'm agree to add a svnignore file.
> 
> Regards
> JB
> 
> On 12/12/2010 02:54 PM, Andreas Pieber wrote:
> >Hey guys,
> >
> >I'm not sure how you feel about git-svn but, for non-commiters they work quite
> >great (I can use and share a running version of karaf for my projects till
> >waiting for my patches to get into the trunk/branches). BUT instead of svn properties
> >git uses .gitignore for ignoring autogenerated files. These can be created, based
> >on the svn ignores,  quite easy by using "git svn create-ignore" (but are also
> >marked as chagned themselves then :( ).
> >
> >How do you feel about including these .gitignore files into the trunk/branches?
> >They wont hurt svn only devs, but help git-svn user, since the changes did not
> >become obfuscated by autogenerated files (or the autogenerated .gitignore
> >files).
> >
> >WDYT?
> >
> >kind regards,
> >andreas
> >

Re: git svn

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Andreas,

at least Guillaume and I use git.

We already commited and updated a .gitignore file containing:

*.i??
.project
.classpath
.settings

I'm gonna add target.

The same .gitignore file is present into the 2.1.x branch.

So I think all is already there. I'm agree to add a svnignore file.

Regards
JB

On 12/12/2010 02:54 PM, Andreas Pieber wrote:
> Hey guys,
>
> I'm not sure how you feel about git-svn but, for non-commiters they work quite
> great (I can use and share a running version of karaf for my projects till
> waiting for my patches to get into the trunk/branches). BUT instead of svn properties
> git uses .gitignore for ignoring autogenerated files. These can be created, based
> on the svn ignores,  quite easy by using "git svn create-ignore" (but are also
> marked as chagned themselves then :( ).
>
> How do you feel about including these .gitignore files into the trunk/branches?
> They wont hurt svn only devs, but help git-svn user, since the changes did not
> become obfuscated by autogenerated files (or the autogenerated .gitignore
> files).
>
> WDYT?
>
> kind regards,
> andreas
>