From: Josef Wolf <jw@raven.inka.de>
To: git@vger.kernel.org
Subject: Rebasing published branches?
Date: Tue, 6 Nov 2012 21:18:22 +0100 [thread overview]
Message-ID: <20121106201822.GE28437@raven.wolf.lan> (raw)
Hello,
I know, I should never rebase published branches. But...
I frequently work on different computers and would like to share my private
branches across them. When done and the feature is in a good shape, I'd like
to rebase to clean up history before I make it available to other people.
I guess rebasing such branches would be OK as long as I can reliably remember
to delete those branches on _all_ the clones I ever created.
But waht if I ever make a mistake? How would one recover from such rebase
disasters? Anybody knows a good description how such a recover would be done?
next reply other threads:[~2012-11-06 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 20:18 Josef Wolf [this message]
2012-11-06 22:53 ` Rebasing published branches? Andrew Ardill
2012-11-06 23:14 ` Antony Male
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=20121106201822.GE28437@raven.wolf.lan \
--to=jw@raven.inka.de \
--cc=git@vger.kernel.org \
/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).