From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org
Subject: Re: [Prism54-devel] Re: [PATCH 4/14 linux-2.6.7-rc1] prism54: add support for avs header in
Date: Thu, 27 May 2004 15:31:00 -0400 [thread overview]
Message-ID: <40B641F4.1040806@pobox.com> (raw)
In-Reply-To: <20040527191649.GT3330@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> On Thu, May 27, 2004 at 02:21:39PM -0400, Jeff Garzik wrote:
>
>>Luis R. Rodriguez wrote:
>>
>>>diff -u -r1.31 -r1.33
>>>--- linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 18 Mar 2004
>>>15:27:44 -0000 1.31
>>>+++ linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 19 Mar 2004
>>>23:03:58 -0000 1.33
>>>@@ -1,4 +1,4 @@
>>>-/* $Header: /var/lib/cvs/prism54-ng/ksrc/islpci_eth.c,v 1.31 2004/03/18
>>>15:27:44 ajfa Exp $
>>>+/* $Header: /var/lib/cvs/prism54-ng/ksrc/islpci_eth.c,v 1.33 2004/03/19
>>>23:03:58 ajfa Exp $
>>
>>
>>Please remove CVS substitions from your code, they cause endless patch
>>rejects if I choose to apply (for example) 10 out of 14 patches.
>
>
> Will do. So if you get
>
> --- ksrc/islpci_eth.c
> +++ ksrc-new/islpci_eth.c
>
> patches, that'll be OK? I substituted ksrc to
> linux-2.6.7-rc1/drivers/net/wireless/prism54 thinking that'll ease your
> job. Sorry for any inconvenience.
I think you misunderstand (and I apologize for causing the confusion).
It is _required_ that the patches include the full path in the header.
You did this correctly:
--- linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 18 Mar
2004 15:27:44 -0000 1.31
+++ linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 19 Mar 2004
I am referring to the CVS substitution variables embedded in your source
code. In this case $Header$.
However, consider what happens when I do:
1) apply patch #1
2) reject patch #2
3) attempt to apply patch #3
If each patch updates the $Header$, then patch #3 cannot be applied
because patch(1) will reject it due to the now-incorrect $Header$ line.
The $Header$ _forces_ me to apply your patches in order, all or none. I
don't think you want that ;-)
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org
Subject: Re: Re: [PATCH 4/14 linux-2.6.7-rc1] prism54: add support for avs header in
Date: Thu, 27 May 2004 15:31:00 -0400 [thread overview]
Message-ID: <40B641F4.1040806@pobox.com> (raw)
In-Reply-To: <20040527191649.GT3330@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> On Thu, May 27, 2004 at 02:21:39PM -0400, Jeff Garzik wrote:
>
>>Luis R. Rodriguez wrote:
>>
>>>diff -u -r1.31 -r1.33
>>>--- linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 18 Mar 2004
>>>15:27:44 -0000 1.31
>>>+++ linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 19 Mar 2004
>>>23:03:58 -0000 1.33
>>>@@ -1,4 +1,4 @@
>>>-/* $Header: /var/lib/cvs/prism54-ng/ksrc/islpci_eth.c,v 1.31 2004/03/18
>>>15:27:44 ajfa Exp $
>>>+/* $Header: /var/lib/cvs/prism54-ng/ksrc/islpci_eth.c,v 1.33 2004/03/19
>>>23:03:58 ajfa Exp $
>>
>>
>>Please remove CVS substitions from your code, they cause endless patch
>>rejects if I choose to apply (for example) 10 out of 14 patches.
>
>
> Will do. So if you get
>
> --- ksrc/islpci_eth.c
> +++ ksrc-new/islpci_eth.c
>
> patches, that'll be OK? I substituted ksrc to
> linux-2.6.7-rc1/drivers/net/wireless/prism54 thinking that'll ease your
> job. Sorry for any inconvenience.
I think you misunderstand (and I apologize for causing the confusion).
It is _required_ that the patches include the full path in the header.
You did this correctly:
--- linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 18 Mar
2004 15:27:44 -0000 1.31
+++ linux-2.6.7-rc1/drivers/net/wireless/prism54/islpci_eth.c 19 Mar 2004
I am referring to the CVS substitution variables embedded in your source
code. In this case $Header$.
However, consider what happens when I do:
1) apply patch #1
2) reject patch #2
3) attempt to apply patch #3
If each patch updates the $Header$, then patch #3 cannot be applied
because patch(1) will reject it due to the now-incorrect $Header$ line.
The $Header$ _forces_ me to apply your patches in order, all or none. I
don't think you want that ;-)
Jeff
next prev parent reply other threads:[~2004-05-27 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 8:31 [PATCH 4/14 linux-2.6.7-rc1] prism54: add support for avs header in Luis R. Rodriguez
2004-05-24 8:31 ` Luis R. Rodriguez
2004-05-27 18:21 ` Jeff Garzik
2004-05-27 19:16 ` [Prism54-devel] " Luis R. Rodriguez
2004-05-27 19:16 ` Luis R. Rodriguez
2004-05-27 19:31 ` Jeff Garzik [this message]
2004-05-27 19:31 ` Jeff Garzik
2004-05-27 19:31 ` CVS tags (was Re: [Prism54-devel] " Valdis.Kletnieks
2004-05-27 19:56 ` Jeff Garzik
2004-05-27 19:56 ` CVS tags (was " Jeff Garzik
2004-05-27 20:01 ` CVS tags (was Re: [Prism54-devel] " Andreas Dilger
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=40B641F4.1040806@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.