Hi,
I wanted to see if anyone thought it would a good idea to add .gitignore files in a few places to make it easier for using Git. Unless I'm missing something (which is highly likely), people who are using Git or git-svn for development are making their own accommodations for keeping built/generated files out of version control. I know at least a few developers are using git-svn, and there's the Git mirror which people might submit patches from, so it seems like it might be worthwhile for the minimal amount of effort. Again, I might have no idea what I'm talking about, so please correct me if that's the case, since I'm really new to using version control systems.
I've attached a patch which might be a good starting point but I've probably missed some files that get generated under certain circumstances.
Cheers, Matthew Brush (codebrainz)
git-svn supports svn:ignore property, perhaps use that instead. See git svn create-ignore/show-ignore.
Best regards.
On 03/08/11 17:55, Thomas Martitz wrote:
git-svn supports svn:ignore property, perhaps use that instead. See git svn create-ignore/show-ignore.
Good to know. But I ran git svn show-ignore and the list of excludes it printed doesn't seem nearly complete. Is it that the svn:ignore properties and/or global-ignore needs to be updated on the SVN repository?
Cheers, Matthew Brush (codebrainz)
Am 09.03.2011 03:44, schrieb Matthew Brush:
On 03/08/11 17:55, Thomas Martitz wrote:
git-svn supports svn:ignore property, perhaps use that instead. See git svn create-ignore/show-ignore.
Good to know. But I ran git svn show-ignore and the list of excludes it printed doesn't seem nearly complete. Is it that the svn:ignore properties and/or global-ignore needs to be updated on the SVN repository?
Yes, most likely the list isn't complete.
Cheers, Frank
On Wed, 09 Mar 2011 11:21:21 +0100, Frank wrote:
Am 09.03.2011 03:44, schrieb Matthew Brush:
On 03/08/11 17:55, Thomas Martitz wrote:
git-svn supports svn:ignore property, perhaps use that instead. See git svn create-ignore/show-ignore.
Good to know. But I ran git svn show-ignore and the list of excludes it printed doesn't seem nearly complete. Is it that the svn:ignore properties and/or global-ignore needs to be updated on the SVN repository?
Yes, most likely the list isn't complete.
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
Just my 2cents.
Regards, Enrico
On 09.03.2011 20:05, Enrico Tröger wrote:
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
That's best accomplished by setting svn:ignore and generating .gitignore from it.
IIRC, if you clone a svn repo with git-svn then it even automatically does this (and puts the ignores into .git/info/exclude).
Best regards.
On Wed, 09 Mar 2011 20:07:26 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 09.03.2011 20:05, Enrico Tröger wrote:
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
That's best accomplished by setting svn:ignore and generating .gitignore from it.
IIRC, if you clone a svn repo with git-svn then it even automatically does this (and puts the ignores into .git/info/exclude).
But based on feedback earlier inside this thread, the svn:ignore list seems not to be complete.
Cheers, Frank
On Wed, 9 Mar 2011 20:15:31 +0100, Frank wrote:
On Wed, 09 Mar 2011 20:07:26 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 09.03.2011 20:05, Enrico Tröger wrote:
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
That's best accomplished by setting svn:ignore and generating .gitignore from it.
IIRC, if you clone a svn repo with git-svn then it even automatically does this (and puts the ignores into .git/info/exclude).
But based on feedback earlier inside this thread, the svn:ignore list seems not to be complete.
This seems like a good time to make it more complete...:D.
Regards, Enrico
On Wed, 9 Mar 2011 20:21:27 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Wed, 9 Mar 2011 20:15:31 +0100, Frank wrote:
On Wed, 09 Mar 2011 20:07:26 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 09.03.2011 20:05, Enrico Tröger wrote:
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
That's best accomplished by setting svn:ignore and generating .gitignore from it.
IIRC, if you clone a svn repo with git-svn then it even automatically does this (and puts the ignores into .git/info/exclude).
But based on feedback earlier inside this thread, the svn:ignore list seems not to be complete.
This seems like a good time to make it more complete...:D.
Dammit. I knew there was something ....
On 03/09/11 11:26, Frank Lanitz wrote:
On Wed, 9 Mar 2011 20:21:27 +0100 Enrico Trögerenrico.troeger@uvena.de wrote:
On Wed, 9 Mar 2011 20:15:31 +0100, Frank wrote:
On Wed, 09 Mar 2011 20:07:26 +0100 Thomas Martitzthomas.martitz@student.htw-berlin.de wrote:
On 09.03.2011 20:05, Enrico Tröger wrote:
I use SVN, so I don't care much about a .gitignore (read: I'm neutral).
I just would suggest, if we use a .gitignore as well (assuming replying svn:ignore won't work as expected with GIT), keep the .gitignore somewhat in sync with the svn:ignore content.
That's best accomplished by setting svn:ignore and generating .gitignore from it.
IIRC, if you clone a svn repo with git-svn then it even automatically does this (and puts the ignores into .git/info/exclude).
But based on feedback earlier inside this thread, the svn:ignore list seems not to be complete.
This seems like a good time to make it more complete...:D.
Dammit. I knew there was something ....
You can use the file/patch I sent on the original message to get a current list of what needs to be excluded/ignored, to update the svn:ignore property. The main problem I see with using the svn:ignore property is that I don't think it's settable for all the people using git-svn (might be able to now, but not from what I read online), so it's unlikely those plugins that generate files that should be ignored are going to have the svn:ignore property updated. The other thing is that anyone using the Git mirror isn't going to get those excludes/ignores, however, having used git-svn for a little bit now, I don't even understand why anyone would use the Git mirror over git-svn for development.
The one thing I do like about .gitignore files is that you can have one global one for the whole project, and then one in each plugin dir that needs one, and then the plugin author just needs to tack on his generated files as required.
I must say, being a newbie to community development and version control, I kinda freaked out bit when I almost commited 50 new files polluting the whole tree with noise on my first commit. Now that I've got my end setup properly, it's not as much of an issue, but hopefully at least it will result in the svn:ignore property being updated and maybe help with DRY for each developer (ie. maintaing their own ignores).
Cheers, Matthew Brush (codebrainz)
On 10.03.2011 02:47, Matthew Brush wrote:
I don't even understand why anyone would use the Git mirror over git-svn for development.
The Git mirror is git-svn :) Cloning the mirror saves you the lengthy procedure of cloning the svn repo via git-svn (because the mirror already did this).
After cloning the Git mirror you can just do:
$ git update-ref refs/remotes/git-svn origin/master $ git svn init|https://geany.svn.sourceforge.net/svnroot/geany/trunk%7C $ git svn fetch
Best regards.