git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Raman Gupta <rocketraman@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: Reference for git.git release process
Date: Wed, 25 Mar 2009 16:41:10 -0700	[thread overview]
Message-ID: <7vocvpw4q1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <49CAAA16.1080401@fastmail.fm> (Raman Gupta's message of "Wed, 25 Mar 2009 18:03:02 -0400")

Raman Gupta <rocketraman@fastmail.fm> 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.

  reply	other threads:[~2009-03-25 23:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:32 Reference for git.git release process Raman Gupta
2009-03-25 19:30 ` Junio C Hamano
2009-03-25 22:03   ` Raman Gupta
2009-03-25 23:41     ` Junio C Hamano [this message]
2009-03-26  3:26       ` Junio C Hamano
2009-03-26  2:27   ` Jeff King
2009-03-26  3:13     ` Junio C Hamano
2009-03-26  3:15       ` Jeff King
2009-03-26  3:28         ` Junio C Hamano
2009-03-26  3:49           ` Jeff King
2009-03-26  3:34     ` Junio C Hamano
2009-03-26 17:03       ` Shawn O. Pearce
2009-03-26  8:05   ` Andreas Ericsson
2009-03-26 14:29     ` Raman Gupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vocvpw4q1.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=rocketraman@fastmail.fm \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).