From: Simon Hausmann <simon@lst.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: merging git-p4 into git/fastimport.git (second try)
Date: Tue, 19 Jun 2007 08:42:09 +0200 [thread overview]
Message-ID: <200706190842.13175.simon@lst.de> (raw)
In-Reply-To: <20070618230018.GA6143@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
On Tuesday 19 June 2007 01:00:18 Shawn O. Pearce wrote:
> Simon Hausmann <simon@lst.de> wrote:
> > after reworking most of the really short commit logs and adding the
> > missing SOB lines I'd like to ask for consideration of merging git-p4 as
> > part of contrib/fastimport/ from
> >
> > git://repo.or.cz/fast-export.git git-p4
>
> Most of the commits look pretty good. The effort you have put into
> cleaning them up shows.
>
> However, many of the oneline descriptions from Han-Wen Nienhuys
> are still really short and not very descriptive. They won't look
> very good in Junio's "What's in git.git". A few of yours are
> also pretty long winded for a typical oneline in git.git, but I'd
> rather have a descriptive-but-long oneline anytime over a short
> and undescriptive one.
Why not just leave out the entire lot of git-p4 logs in "What's in git.git"
this one time? I'm not sure of how much value it is at this point anyway. I'm
just interested in preserving the history to ease debugging.
> So I'm seriously considering merging this at this point. I'm heading
> out to dinner and will look at it more again when I get back, but
> I think we should just bite the bullet and bring it into core Git.
There's also another option that might help to keep the logs clean for future
plain "git log" usage and that is to prepend a "git-p4:" prefix to most of
the logs. That makes "git-p4: Documentation cleanups" look better I think and
it's really easy to do.
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-19 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 22:35 merging git-p4 into git/fastimport.git (second try) Simon Hausmann
2007-06-18 23:00 ` Shawn O. Pearce
2007-06-19 6:42 ` Simon Hausmann [this message]
2007-06-22 23:20 ` Shawn O. Pearce
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=200706190842.13175.simon@lst.de \
--to=simon@lst.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).