From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/3] readline-6.2 rebase
Date: Wed, 11 May 2011 06:04:00 -0000 [thread overview]
Message-ID: <20110511060421.GA9857@host1.jankratochvil.net> (raw)
In-Reply-To: <m339knu7vm.fsf@fleche.redhat.com>
On Mon, 09 May 2011 19:00:13 +0200, Tom Tromey wrote:
> FWIW I think this is the best time to check this in, because the release
> branch has been made.
Do you think it should be checked in as separate patches (to unchanged
readline-6.2 with each of the patches applied afterwards) or as a single
commit?
The previous import was a single-commit one with sourceware patches already
contained:
commit c6fad60c72bac0b0ba1b7912f866caa3a6cb744c
Author: Daniel Jacobowitz <dan@debian.org>
Date: Fri May 5 18:26:14 2006 +0000
Readline 5.1 import for HEAD.
Advantage of the single commit is it does not introduce intermedia regressions
which makes it compatible with `git bisect'. (OTOH git bisect has various
issues with building older snapshots on recent systems and also I am not sure
if all the multi-part patches are per-piece regression+buildability safe.)
Advantage of the multiple commits is sure more clear import for futher rebases
and reviews. Porting the readline-5.1 patchset was a bit of reverse
engineering with GIT.
(I am more for the latter choice now; despite I proposed the former before.)
Thanks,
Jan
next prev parent reply other threads:[~2011-05-11 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 12:29 Jan Kratochvil
2011-05-09 17:00 ` Tom Tromey
2011-05-11 6:04 ` Jan Kratochvil [this message]
2011-05-11 16:36 ` Joel Brobecker
2011-05-11 17:15 ` Jan Kratochvil
2011-05-11 23:44 ` [commit] " Jan Kratochvil
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=20110511060421.GA9857@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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