Hi, On Tue, 24 Apr 2007, Daniel Barkalow wrote: > On Tue, 24 Apr 2007, Johannes Schindelin wrote: > > > Hi, > > > > On Mon, 23 Apr 2007, Junio C Hamano wrote: > > > > > As with any "tracking" list, wanting to have one and starting is the > > > easy part. Unless kept up to date, such a list becomes quickly useless, > > > or even worse than not having one, leading to wasted wild goose chase if > > > people look at it without knowing how stale it is. > > > > I used to issue `git log -p todo -- TODO` quite a lot; thank you! > > > > And I miss kernel and git cousins, too... > > Why not have the TODO list in the source branches, listing features that > ought to be in that version but aren't? That way, people can submit > feature requests as patches that add to the todo list (and the requested > feature can be discussed in response), and patches that implement > features can simultaneously remove them from the todo list. Anyone > considering working on adding desired features would need an up-to-date > repository anyway. Like Junio said, it is not starting it, but maintaining. (BTW Andy, I am still waiting for that list...) Judging from my own failings in updating the documentation when doing patches, I have no doubt I would miss out on the TODO, too. Ciao, Dscho - 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