From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: 2.6.19-rcX vs 2.6.20
Date: Tue, 24 Oct 2006 08:54:32 +0000 [thread overview]
Message-ID: <200610240954.32895@strip-the-willow> (raw)
In-Reply-To: <200610240848.47708@strip-the-willow>
Hi Ian
Thanks for the tip, I know your web repository and will certainly look at
stgit (I am doing something like that at the moment).
| I would like to see bug fixes in 2.6.19 too if they are obvious fixes
| e.g. the one I sent today. I won't get into the debate about other
| cosmetic ones....
The problem is not in cosmetics. Each new patch potentially changes offsets
and contexts of outstanding ones (cosmetic or not), so doing `x' now will
imply having to re-do `y' at a later time, whereas my idea was to to both `x' and
`y' at one time.
To make a start, I will submit the batch of what I have (but explicitly not for 2.6.19)
so that hopefully the patch situation can be a little clarified.
Gerrit
prev parent reply other threads:[~2006-10-24 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 7:48 2.6.19-rcX vs 2.6.20 Gerrit Renker
2006-10-24 7:53 ` Arnaldo Carvalho de Melo
2006-10-24 8:12 ` Gerrit Renker
2006-10-24 8:23 ` Ian McDonald
2006-10-24 8:54 ` Gerrit Renker [this message]
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=200610240954.32895@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.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