From: Junio C Hamano Date: Wed, 25 Mar 2009 23:41:10 GMT Subject: Re: Reference for git.git release process Message-ID: <7vocvpw4q1.fsf@gitster.siamese.dyndns.org> In-Reply-To: <49CAAA16.1080401@fastmail.fm> Raman Gupta writes: > Junio C Hamano wrote: > ... >> That is more-or-less correct, even though I'd actually do either >> >> git branch -f next master >> >> or >> >> git checkout next >> git reset --hard master >> >> instead of deleting and recreating. > > Is that a stylistic preference or does your approach have some > advantage over the delete/create? Doesn't git branch -f internally > delete and re-create? No, yes, and no. The last answer "no" relates to the fact that the preservation of the reflog and per-branch configuration for "next", which is the reason behind the second answer "yes". > ... The only > concern I had with this workflow was the difficult to understand > visualization of the history. So to repeat my earlier question: Are > there some canned gitk invocations, or other tips/tricks/approaches,... I do not share the difficulty, and there is no answer from me to your "earlier" question. Perhaps other people have some tips.