From: Alex Riesen <raa.lkml@gmail.com>
To: Romano Giannetti <romano@dea.icai.upcomillas.es>
Cc: git@vger.kernel.org
Subject: Re: Two newbie question: "dead" branches and merging after cherry-pick.
Date: Fri, 27 Jan 2006 20:47:30 +0100 [thread overview]
Message-ID: <20060127194730.GB6169@steel.home> (raw)
In-Reply-To: <20060127173619.GA26199@pern.dea.icai.upcomillas.es>
Romano Giannetti, Fri, Jan 27, 2006 18:36:19 +0100:
> - I use to work on a topic branch to make test, try solutions for
> bugs, etc. Say I am done with the branch "test-bill-idea". I decide
> it's a dead branch, so that I do not want to see it in day-by-day
> work (git branch, basically), but I do not want to loose it. If I
> delete the branch I will loose all its commit at the next prune,
> correct? There is a way to maintain it as a dead or hidden branch,
> shown for example just by gitk --all? If I tag the tip of the
> branch, and then delete .git/refs/head/test-bill-idea, will the
> "dead branch commits" be preserved by next prune(s)?
Yes, it will.
You can actually move the reference file anywhere under .git/refs/,
and "git prune" will never touch it and gitk will show it different
color (looks grey to me). The tags are shown yellow, which can be
associated with "dead for some time" already.
> - Easier: suppose I cheery-picked "abababab" from branch "testing"
> to master branch. What will happen if later I decide to merge
> all "testing" to master branch? I will have a merge conflict (trying
> to apply two times the same fix) or not?
Yes, you probably will have to deal with a conflict (it can match the
branch to be merged exactly, which is hardly a conflict).
next prev parent reply other threads:[~2006-01-27 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 17:36 Two newbie question: "dead" branches and merging after cherry-pick Romano Giannetti
2006-01-27 19:47 ` Alex Riesen [this message]
2006-01-27 20:59 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 11:44 Romano Giannetti
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=20060127194730.GB6169@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=romano@dea.icai.upcomillas.es \
/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