Adam Spiers

OK, thanks. Much as I'd love the excuse to learn Scala or Haskell, I'm in a similar boat to you regards free time :-/ BTW I have had good experiences...

Now that I think about it more, it seems to me that adding a tag to the base of the topic branch seems like the cleanest solution. This would solve...

@greenrd But what if I don't want to squash my topic into a single commit? That's generally a bad idea if the topic contains multiple logical changes. And it also...

@imz In reply to your points: 1. Fantastic - thanks for the info which seems to prove that my thinking is along the right lines! 2. If we used tags,...

I am working on this issue this week as a [Hack Week](https://hackweek.suse.com/) project. > I'm still undecided whether it should be one or two tags per topic though. I think...

Another advantage of keeping the description and dependencies coupled together in the same chunk of metadata is that they can't accidentally get separated, e.g. when transferring between remotes, or if...

One immediate observation is that tracking changes to metadata is supposed to be handled by the reflog, not the normal log. But the key question here is, what are the...

On Wed, Apr 15, 2015 at 03:59:28AM -0700, Robin Green wrote: > > it might occasionally be useful to be able to merge the differences if the .topmsg is intended...

> > Why? We don't automatically run `tg update` if the contents of an existing dependency gets changed, so why automatically run it if a new dependency is introduced. >...

@hrj Sorry for the very slow reply! My work will always be found at https://github.com/aspiers/topgit/branches but I can't remember what state I last left it in. I am hoping to...