From: Matthias Hopf <mhopf@suse.de>
To: git@vger.kernel.org
Cc: xorg@lists.freedesktop.org
Subject: git-rebase nukes multiline comments
Date: Fri, 16 Jun 2006 19:12:51 +0200 [thread overview]
Message-ID: <20060616171251.GA29820@suse.de> (raw)
Hi all,
I'm using git-1.2.4 on SL10.1, in centralized style development (for X.org).
I wanted to commit a set of changes (4 local commits) upstream, so I had
to do a git-rebase first (in that particular case a git-pull would have
been possible as well, but git-rebase fits the CVS style development
better). After git-fetch, git-rebase origin, and git-push all my changes
had only the first line of the changelog comment, the remainder was
nuked.
To reproduce:
mkdir /var/tmp/blaup
cd /var/tmp/blaup
git-init-db
echo test > foo
git-add foo
git-commit (any comment)
cd ..
git-clone /var/tmp/blaup bla
cd bla
echo test2 >>foo
git-commit foo (multiline comment)
cd ../blaup
echo test3 >bar
git-add bar
git-commit (any comment)
cd ../bla
git-fetch
git-log (shows multiline comment for 'test2')
git-rebase origin
git-log (shows only the first line of the multiline comment!)
I doubt this is intended behavior.
Also, while trying to reproduce this with the original upstream
repository, I would have had to git-fetch my origin branch (upstream
master), but not to get _all_ new commits, but only up to a certain
revspec (the one *before* my own commits).
I tried "git-fetch <refspec>:", but this didn't work, neither did
anything else I tried. This is clearly beyond my understanding of git,
so how can this be done?
Thanks
Matthias
--
Matthias Hopf <mhopf@suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
next reply other threads:[~2006-06-16 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 17:12 Matthias Hopf [this message]
2006-06-16 17:23 ` git-rebase nukes multiline comments David Kowis
2006-06-16 17:55 ` David Kowis
2006-06-19 9:36 ` Matthias Hopf
2006-06-19 9:54 ` Matthias Hopf
2006-06-16 21:25 ` Junio C Hamano
2006-06-16 21:56 ` David Kowis
2006-06-16 23:21 ` Junio C Hamano
2006-06-19 9:53 ` Matthias Hopf
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=20060616171251.GA29820@suse.de \
--to=mhopf@suse.de \
--cc=git@vger.kernel.org \
--cc=xorg@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.