[MonoDevelop] Autogeneration of .gitignore for MD projects

Andy andy at ninjagod.com
Mon Apr 27 14:58:15 EDT 2009


I see that "git add ." doesen't seem to be the most suitable one. A lot of
tutorials and guides seemed to prefer that method, thanks for telling me
about the new commands, and they seem to work as expected.

And the gitignore you specified is essentially the same I have for my
project. I was moving the MD sources to a branch for my own test commits,
and since it uses autotools, a lot of files are modified. I found running
"git status >> .gitignore" after the build wrote an unformatted list of all
changed files, which I could conviniently ignore, but I kept thinking there
has to be a better way.

It would be best for the git plugin for MD check wether the current project
is being tracked as a repository (usually when people init the repository
after having some sources already existing.) and then write a gitignore if
the user wants it to be written specifically.

I think this would be best as part of the managed git project. Do let me
know when this feature is in place, I don't think it would take too long to


On Tue, Apr 28, 2009 at 12:09 AM, Jan Hudec <bulb at ucw.cz> wrote:

> Andy <andy <at> ninjagod.com> writes:
> > Hi,I use git to track two MD projects. If you have used git, you probably
> > know that to stage changes into a commit, you have to add them - each
> time
> > you make a commit. You can either add all the files that have changed or
> add
> > them individually. Most people do "git add ." which does the former.
> I can't confirm that (*). I have not done any survey, but I don't think
> 'git add .' would be a particularly common thing to do.
> You can either use 'git commit -a', which gives you the same behaviour as
> 'svn commit', namely it updates all files git already knew about, but does
> not add any new ones. Or you can use 'git add -u', which is the same thing,
> without the commit bit.
> But my impression is, that git hackers actually add individual files
> whenever
> they get them in some consistent state, often even carefuly pick individual
> hunks with 'git add -i' (or use the equivalent operations in git gui).
> All that said, the ignore list is indeed a good thing. But it should mostly
> be constant for all MD projects. So far I get away with:
> bin
> *.md.pc
> *.pidb
> *.userprefs
> *.usertasks
> (I did not try any installer or localization projects yet, so there may be
> a
> few extras, but it should be mostly constant for each project type.)
> Jan
> (*) I've followed git mailing list for some time, read quite a bit about it
> and understand most of the principles.
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list

Anirudh Sanjeev
Fourth Year Undergrad - Indian Institute of Technology Kharagpur
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20090428/992f7c80/attachment-0001.html 

More information about the Monodevelop-list mailing list