Hi, My git knowledge is pretty accurately described by http://xkcd.com/1597/ , so the first time I'll do that branching and merging (esp. the latter) it'd be great if someone double checked on me.
Also: What are the steps to be performed before/after a commit? I mean, run the unittests (make tests -- that's it?), check if the code is formatted (make indent -- correct?), update the NEWS file (how?), anything else? thanks, egmont On Sun, Nov 8, 2015 at 9:49 PM, Yury V. Zaytsev <y...@shurup.com> wrote: > On Fri, 2015-11-06 at 19:43 +0100, Egmont Koblinger wrote: > >> For minor changes, such as a followup bugfix in the viewer (e.g. 3531) >> I wouldn't want to wait for more than a couple of days; let's say a >> week at most. Does this sound okay? > > A week would be fine with me for minor changes, and I trust your > judgment on what's minor enough... sadly, I can't keep track of changes > on this timescale, but hopefully Andrew will keep an eye and yell if > something goes very very wrong. > > You probably already know this, but there is a helpful report page on > Trac which among other things can show tickets waiting for a review... > you can use that to check for tickets that need feedback. > > As far as I can see, you've accepted the GitHub invitation, so you > should have access to the repository by now, and you've got Trac admin > privileges as well, so that you can ravage the tickets and the wiki. > > Let me know if there is anything else I can do for you. I'll be checking > the mailing lists from time to time, but one way to catch my attention > in the case of emergency is to put me explicitly on CC. > > -- > Sincerely yours, > Yury V. Zaytsev > > _______________________________________________ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
