From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: <paulus@samba.org>
Cc: "Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BK Id header removals causes patch to fail!
Date: Tue, 29 Apr 2003 00:53:13 +0200 [thread overview]
Message-ID: <001301c30dd8$f5f691e0$020120b0@jockeXP> (raw)
In-Reply-To: 16045.43640.243207.193539@nanango.paulus.ozlabs.org
> Joakim Tjernlund writes:
>
> > > A typical BK Id in a file looks likes this:
> > >
> > > And in the patch it looks like this:
> > > /*
> > > * BK Id: SCCS/s.setup.c 1.111 10/29/02 10:49:05 trini
> > > */
> > >
> > > And the patch:
> > > @@ -1,7 +1,4 @@
> > > /*
> > > - * BK Id: %F% %I% %G% %U% %#%
> > > - */
> > > -/*
> > >
> > > Jocke
> >
> > I can't find BK command/option which will fix this problem.
> > What was the rationale behind this pointless cleanup? I can understand if
> > you do this in 2.5 but why do it in 2.4?
> >
> > Is there a way to fix this using BK?
>
> I assume you mean that it looks like SCCS/s.setup.c ... in the file
> and %F% ... in the patch.
Yes, sorry for the cut and paste error
>
> Try doing a 'bk -r get -k' in the tree that you are patching before
> you patch. That should get all the files in the %F% ... form.
hmm, the tree I am patching is a CVS tree. I can't get these in %F% form with CVS.
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-28 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 11:19 BK Id header removals causes patch to fail! Joakim Tjernlund
2003-04-28 13:44 ` Joakim Tjernlund
2003-04-28 22:26 ` Paul Mackerras
2003-04-28 22:53 ` Joakim Tjernlund [this message]
2003-04-29 0:56 ` Paul Mackerras
2003-04-29 18:11 ` Tom Rini
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='001301c30dd8$f5f691e0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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