From: Andreas Dilger <adilger@clusterfs.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org
Subject: Re: CVS tags (was Re: [Prism54-devel] Re: [PATCH 4/14 linux-2.6.7-rc1] prism54: add support for avs header in
Date: Thu, 27 May 2004 14:01:59 -0600 [thread overview]
Message-ID: <20040527200159.GP2603@schnapps.adilger.int> (raw)
In-Reply-To: <200405271931.i4RJVjYB002642@turing-police.cc.vt.edu>
On May 27, 2004 15:31 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 27 May 2004 15:16:49 EDT, Luis R. Rodriguez said:
> > --- ksrc/islpci_eth.c
> > +++ ksrc-new/islpci_eth.c
>
> I think this was what he referred to:
>
> >-/* $Header: /var/lib/cvs/prism54-ng/ksrc/islpci_eth.c,v 1.31 2004/03 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 $
>
> as this will almost surely cause rejects (sooner or later) unless 100% of your
> patches are applied and in the right order.
This also causes grief if this file is ever imported again into a CVS-based
SCM, unless you remember to do so with -ko.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2004-05-27 20:02 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 ` [Prism54-devel] " Jeff Garzik
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 ` Andreas Dilger [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=20040527200159.GP2603@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--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.