Oh well, I know for the future to commit after init from a remote. At least we've got the code, even if the history is a funny loop instead of a tree. :)
Speaking of the code, any feedback on the implementation? Does anyone besides me think we should remove the ability to make multiple variations with the same coordinates? If not, why not (and how should Guess Mode work in that case, as the result is currently semi-undefined from the user's perspective -- it goes to the first variation it hits in the SGF_NEXT direction, but is that expected?) Ethan On Mon, 2009-09-21 at 22:05 -0400, Michel Alexandre Salim wrote: > On Mon, Sep 21, 2009 at 7:48 PM, Michel Alexandre Salim > <[email protected]> wrote: > > On Mon, Sep 21, 2009 at 1:11 AM, Joseph Piché <[email protected]> wrote: > >> After a busy weekend of working a bunch of other things, I finally got > >> around to trying to figure out git, and I believe I've merged the > >> changes. But of course only after that did I see the comments made on > >> the merge request. So, if something needs to be done differently, > >> please let me know. > >> > > My fault, I didn't get round to doing it in time. I'll see what I can do. > > > OK, following up: I found a way to undo the revisions on my local > repository, but it looks like it's impossible to do that on the > Gitorious repository, short of removing the current repository, > creating a replacement and pushing the fixed repository to it. Which > is way overkill. > > I guess the best solution is just to leave the current commits in > place. It'd be nice of Gitorious have a way for a merge request to be > assigned to someone, but I guess what I could have done is to close > the request, to make sure it did not get committed verbatim. > > Best, > _______________________________________________ Quarry-dev mailing list [email protected] https://mail.gna.org/listinfo/quarry-dev
