From: Miklos Vajna <vmiklos@frugalware.org>
To: Rick Moynihan <rick@calicojack.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Rebasing Multiple branches at once...
Date: Thu, 16 Oct 2008 23:00:02 +0200 [thread overview]
Message-ID: <20081016210002.GJ536@genesis.frugalware.org> (raw)
In-Reply-To: <48F7542B.1050909@calicojack.co.uk>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Thu, Oct 16, 2008 at 03:48:11PM +0100, Rick Moynihan <rick@calicojack.co.uk> wrote:
> Yes, but my understanding is that it's only harmful if you publish the
> branch (or dependent branches) which are being rebased.
>
> So rebasing is very bad in these circumstances, but I fail to see why it's
> bad if these branches are kept private.
Ah, I thought you publish your branches.
One reason may be that if you use merge, no history is lost, if you use
rebase, history is in the reflogs, so it'll be lost after some time. But
if you know what you are doing, then this is not a problem.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-16 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 12:17 Rebasing Multiple branches at once Rick Moynihan
2008-10-16 13:59 ` Miklos Vajna
2008-10-16 14:48 ` Rick Moynihan
2008-10-16 21:00 ` Miklos Vajna [this message]
2008-10-17 2:00 ` Junio C Hamano
2008-10-16 13:59 ` David Kastrup
2008-10-16 14:57 ` Rick Moynihan
2008-10-16 15:02 ` Robin Burchell
2008-10-16 20:27 ` Toby Allsopp
-- strict thread matches above, loose matches on Subject: below --
2016-12-31 8:14 Rebasing multiple " Mike Hommey
2017-01-01 2:40 ` Junio C Hamano
2017-01-02 6:42 ` Jeff King
2017-01-01 8:42 ` Johannes Sixt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081016210002.GJ536@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=rick@calicojack.co.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).