public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Koschewski <marc@osknowledge.org>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Marc Koschewski <marc@osknowledge.org>,
	dtor_core@ameritech.net, rlrevell@joe-job.com,
	76306.1226@compuserve.com, akpm@osdl.org,
	linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: Wanted: hotfixes for -mm kernels
Date: Sun, 5 Feb 2006 09:56:49 +0100	[thread overview]
Message-ID: <20060205085648.GA5663@stiffy.osknowledge.org> (raw)
In-Reply-To: <43E4FF13.2050206@mbligh.org>

* Martin J. Bligh <mbligh@mbligh.org> [2006-02-04 11:22:59 -0800]:

> 
> >We talked about hotfixes for -mm. So why not check these into the -mm-git 
> >tree
> >then? This would make sense and would conform fully to my understanding of 
> >what
> >the -mm-git tree should be. I don't want to select 23 patches from LKML to 
> >make
> >the tree compile or work. I want to checkout. Why make it easy when you 
> >may get
> >it difficult.
> >
> >Besides testing the stuff we would get more far by being able to test 
> >stuff faster
> >(because a patch is applied to -mm and we do a checkout) instead of 
> >waiting a
> >week for this mega-patch to be applied.
> >
> >What sense does an -mm tree make when there are people that cannot test it 
> >because of
> >known bugs that lead to the -mm tree not being bootable or - even worse - 
> >destroying
> >the system?
> >
> >git is you friend. Not only for Linus' tree, but as well for Andrew's tree.
> >It would just make debugging and testing -mm more convenient and less time
> >consuming for the testers. Instead of 1000 people seeking patches Andrew 
> >would
> >just check in and we all could pull it.
> >
> >If you agree with me or not - that's what I think.
> 
> SCMs don't fix anything. The real work is in selecting patches and 
> merging them. Frankly,  I test a lot of stuff myself, and the tarballs 
> are  a damned sight easier to work with, and have a simple chronological 
> timeline to work from.

To me it would be easier if I could use a repository that get's updated every
day (or several times a day) than wait a week for the patch to be available.

Moreover, a repository in fact _is_ easyier when it comes to debugging than is a
tarball or such. What if one says 'Gimme that driver 6 weeks ago'? See ... with
a repository I could just get it whereas with patches I have to read lots of
mails to get a clue when stuff got applied (in the tree and over here on my hard
disk).

I didn't mean to start a discussion here. I was just telling you what is easier
for me. Anyone has it's own style of coding. Someone likes patches, others
just live with them. My boss doesn't like vi either. So I may not use it? Puh!

Marc

  reply	other threads:[~2006-02-05  8:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 20:00 Wanted: hotfixes for -mm kernels Chuck Ebbert
2006-02-02 20:53 ` Lee Revell
2006-02-02 21:45   ` Dmitry Torokhov
2006-02-02 21:48     ` Randy.Dunlap
2006-02-02 21:57       ` Dmitry Torokhov
2006-02-03 10:07     ` Marc Koschewski
2006-02-04 16:37       ` Martin J. Bligh
2006-02-04 18:57         ` Marc Koschewski
2006-02-04 19:22           ` Martin J. Bligh
2006-02-05  8:56             ` Marc Koschewski [this message]
2006-02-04 20:41           ` Adrian Bunk
2006-02-05  9:09             ` Marc Koschewski
2006-02-05 15:13               ` Adrian Bunk
2006-02-05  2:56         ` Paul Jackson
2006-02-05  8:58           ` Marc Koschewski
2006-02-05 15:58             ` Martin J. Bligh
2006-02-05 17:15               ` Paul Jackson
  -- strict thread matches above, loose matches on Subject: below --
2006-02-02 22:08 Chuck Ebbert
2006-02-02 22:29 ` Andrew Morton

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=20060205085648.GA5663@stiffy.osknowledge.org \
    --to=marc@osknowledge.org \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=rdunlap@xenotime.net \
    --cc=rlrevell@joe-job.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