Re: [twmode-users-en] About `twittering-retrieve-image'

[Yuto H. <y.h...@gm...>]

> The fix was quite simple after all :)
> 
> http://git.igalia.com/cgi-bin/gitweb.cgi?p=user/berto/twittering-mode.git;a=commitdiff;h=c29a3219d7f176c5d66e53553afab49451a41f5e;hp=dc5c820d6be4f78bb311727139141a75153b51fc

Thanks a lot. I applied it.


> I admit that I don't understand it... there are branches with just one
> commit, it appears to me that the problem is that most (if not all)
> should have been rebased before being merged to master.

Ah, I understand. If all topic branches are rebased to the trunk,
merging them does not result in a messy graph, but a linear
history. right?

I think it's a better way. I will adopt it. Thanks for your
advice.

----
Yuto Hayamizu

Master's degree student at Kitsuregawa Laboratory
Department of Information and Communication Engineering
Graduate School of Information Science and Technology
University of Tokyo

From: Alberto Garcia <ag...@ig...>
Subject: Re: [twmode-users-en] About `twittering-retrieve-image'
Date: Sat, 12 Dec 2009 01:38:02 +0100

> On Fri, Dec 11, 2009 at 09:56:42AM +0900, Yuto Hayamizu wrote:
> 
>> > The new `twittering-retrieve-image' function is great, although it
>> > has a minor annoyance: it leaves a buffer opened with every new
>> > image that is downloaded.
>> > 
>> > I guess it can be easily fixed, but I haven't looked into the code
>> > yet. I can try to write a patch in the next few days.
>> 
>> Nice :)
> 
> The fix was quite simple after all :)
> 
> http://git.igalia.com/cgi-bin/gitweb.cgi?p=user/berto/twittering-mode.git;a=commitdiff;h=c29a3219d7f176c5d66e53553afab49451a41f5e;hp=dc5c820d6be4f78bb311727139141a75153b51fc
> 
>> > BTW, it appears to me that the git repository is a bit of a mess
>> > :) There are so many branches and merges that it's difficult to
>> > follow the progress of the project.
>> 
>> It seems messy in a measure, there's a simple convention and it
>> works for me. The main branch, or trunk, is hayamiz/master, and
>> contributors send pull requests when they write new features or bug
>> fixes.
> 
> I admit that I don't understand it... there are branches with just one
> commit, it appears to me that the problem is that most (if not all)
> should have been rebased before being merged to master.
> 
> It's impossible for me to follow the evolution of the project with a
> history like this:
> 
> http://i49.tinypic.com/iener6.jpg
> 
> Of course this is just my opinion and you have the ultimate decision,
> but I honestly can't think of any good reason why such a small project
> would need all those branches and merges in its repository.
> 
> All of the projects I'm familiar with (including much larger projects
> such as GTK+) have a development history which is essentially linear.
> 
> Berto
> 
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> twmode-users-en mailing list
> twm...@li...
> https://lists.sourceforge.net/lists/listinfo/twmode-users-en