From: Kumar Gala <kumar.gala@freescale.com>
To: "Kumar Gala" <kumar.gala@freescale.com>
Cc: <linux-kernel@vger.kernel.org>, "Jeff Garzik" <jgarzik@pobox.com>,
<akpm@osdl.org>
Subject: Re: [PATCH] Make gcapatch work for all bk transports
Date: Tue, 4 Jan 2005 10:09:56 -0600 [thread overview]
Message-ID: <138B63BE-5E6B-11D9-BC22-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0412181239400.2707-100000@sysperf.somerset.sps.mot.com>
Jeff,
Did you have any issues with this following change to gcapatch? If
not, I'll resend the patch to akpm.
- kumar
On Dec 18, 2004, at 12:42 PM, Kumar Gala wrote:
> Jeff,
>
> I didn't even think if your case. How about extracting out the
> transport
> from 'bk parent -p' as a middle ground. I dont think this will help
> your
> case. If not, we can leave the script as is.
>
> - kumar
>
> Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
>
> diff -Nru a/Documentation/BK-usage/gcapatch
> b/Documentation/BK-usage/gcapatch
> --- a/Documentation/BK-usage/gcapatch 2004-12-18 12:39:32 -06:00
> +++ b/Documentation/BK-usage/gcapatch 2004-12-18 12:39:32 -06:00
> @@ -5,4 +5,4 @@
> # Usage: gcapatch > foo.patch
> #
>
> -bk export -tpatch -hdu -r`bk repogca
> bk://linux.bkbits.net/linux-2.5`,+
> +bk export -tpatch -hdu -r$(bk repogca $(bk parent -p|cut -d:
> -f1)://linux.bkbits.net/linux-2.5),+
>
> On Fri, 17 Dec 2004, Jeff Garzik wrote:
>
> > Kumar Gala wrote:
> > > Andrew,
> > >
> > > Makes the gcapatch script work for any bk transport (including
> http).
> > >
> > > Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
> > >
> > > --
> > >
> > > diff -Nru a/Documentation/BK-usage/gcapatch
> > b/Documentation/BK-usage/gcapatch
> > > --- a/Documentation/BK-usage/gcapatch 2004-12-17 13:42:32
> -06:00
> > > +++ b/Documentation/BK-usage/gcapatch 2004-12-17 13:42:32
> -06:00
> > > @@ -5,4 +5,4 @@
> > > # Usage: gcapatch > foo.patch
> > > #
> > >
> > > -bk export -tpatch -hdu -r`bk repogca
> > bk://linux.bkbits.net/linux-2.5`,+
> > > +bk export -tpatch -hdu -r$(bk repogca $(bk parent -p)),+
> >
> > It's an example script, meant to be modified to suit your local
> tastes.
> >
> > Your patch isn't useful for situations (such as mine :)) where you
> have
> > more than one level of parent, but you want to generate a patch
> versus
> > mainline (not the parent).
> >
> > Jeff
> >
> >
next prev parent reply other threads:[~2005-01-04 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 19:47 [PATCH] Make gcapatch work for all bk transports Kumar Gala
2004-12-17 22:44 ` Jeff Garzik
2004-12-18 18:42 ` Kumar Gala
2004-12-18 19:27 ` Kevin P. Fleming
2005-01-04 16:09 ` Kumar Gala [this message]
2005-01-06 22:49 ` Jeff Garzik
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=138B63BE-5E6B-11D9-BC22-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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