hello, On Wed, Mar 11, 2009 at 11:26 AM, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > On Wed, 11 Mar 2009, Saurabh Gupta wrote: > > > > > /*About GSoC GIT ideas; > > */Here are the ideas which I found to be interested in. Although, I > > would like to discuss any other idea than these in GIT organization. > > > > *1) Domain specific merge helpers* > > Intelligence in the merger can be put which modifies the source file > > according the format. Different file formats can be put in the merger > > to support. > > This is something I've thought would be really handy for making git more > widely useful. The hard part, of course, is coming up with useful > alternative merge algorithms which work for formats that the usual merge > doesn't handle. The infrastructure is mostly there (git supports declaring > the types of files), but there's no point in support for running a > type-specific merger until there are actually type-specific mergers to > run. > > Do you have ideas on what formats you'd try to merge, and how? Well, What I think is to implement file formats other than text like that written on wiki i.e. latex, xml, or even any database file (db file). Another idea (although it can be weired also) is to implement the new file formats in the plug-in formats. For example, to incorporate the merger engine for a new file format, a plug-in is created and can be integrated with the present merger in the git. However, I am not sure how much valid is this idea to make the present merger in git to be compatible with the plug-ins for enabling newer file formats. Any new idea or suggestions are welcome. -- Saurabh Gupta Senior, Electronics and Communication Engg. NSIT,New Delhi, India -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
