Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Reference for git.git release process

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:46:28

Raman Gupta [off-list ref] writes:
Junio C Hamano wrote:
...
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help