git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Hopf <mhopf@suse.de>
To: git@vger.kernel.org
Cc: xorg@lists.freedesktop.org
Subject: Re: git-rebase nukes multiline comments
Date: Mon, 19 Jun 2006 11:36:23 +0200	[thread overview]
Message-ID: <20060619093623.GA15209@suse.de> (raw)
In-Reply-To: <4492F09F.9080906@shlrm.org>

On Jun 16, 06 12:55:43 -0500, David Kowis wrote:
> > I'm new to git, but I tried what you said.
> > my git log:
> > commit c846bea8c61bec7cf0f7688c48abc42577b9ac7f
> > Author: David Kowis <dkowis@kain.org>
> > Date:   Fri Jun 16 12:20:08 2006 -0500
> > 
> >     this is a multi
> > 
> >     line comment
> >     with three lines
> > 
> > 
> > I'm using git 1.4.0. It added a blank line in there...

O-key. Did this work w/o a blank line as well? Then we can assume this
solved in 1.4.0. Now there's still the question whether the log messages
in the upstream archive can be restored...

> I'm going to note that the xorg ML cc doesn't work for anyone not
> subscribed... You may miss out on replies.

I'm subscribed here as well :-)
I just CC'ed xorg so people over there know about the issue as well.

CU

Matthias

-- 
Matthias Hopf <mhopf@suse.de>       __        __   __
Maxfeldstr. 5 / 90409 Nuernberg    (_   | |  (_   |__         mat@mshopf.de
Phone +49-911-74053-715            __)  |_|  __)  |__  labs   www.mshopf.de

  reply	other threads:[~2006-06-19  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 17:12 git-rebase nukes multiline comments Matthias Hopf
2006-06-16 17:23 ` David Kowis
2006-06-16 17:55   ` David Kowis
2006-06-19  9:36     ` Matthias Hopf [this message]
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=20060619093623.GA15209@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 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).