On Thu, 21 Apr 2011 09:57:37 +0200 Tom Willemsen <[email protected]> wrote:
> > Second thing is- wondering if you could rebase your work on the > > latest code. You branched quite a while ago and I'd prefer one line > > of clean code that applies nicely, as it is a lot easier to follow. > > Something like "git rebase master <mybranch>" should do the trick. > > It would also be great if you could use "git rebase -i" or any > > other tricks to squash fixup commits into the proper commit where > > that work originally belonged. > > I'll try, never used rebase before. it's very cool stuff that allows you to clean your history nicely. there are some good tutorials on `git rebase -i`, but if it's your first time, i would suggest to make a backup first, it could get confusing if there are merge conflicts during the rebase. > > * rtf ? I like this even less than isotests as far as WTF naming; I > > had NO idea what that meant until I saw your commit. Why not just > > "releng"? > > Just "releng"? Seems too generic, this app only deals with a small > part of releng, the "releng-testbuild-feedback". Wouldn't that be > preferable? I'ld say: "rtf" in the url (foo.bar/rtf/) and "Releng Testbuild Feedback" as title on the page. If/when we link to this app from other pages, we could use "releng testbuild feedback" for the links. Clear enough imho. Dieter
