From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make gcapatch work for all bk transports
Date: Sat, 18 Dec 2004 12:27:25 -0700 [thread overview]
Message-ID: <41C4849D.9060207@starnetworks.us> (raw)
In-Reply-To: <Pine.GSO.4.44.0412181239400.2707-100000@sysperf.somerset.sps.mot.com>
Kumar Gala wrote:
> 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.
It would actually be nice if bk supported a method to get the "root"
parent path from any clone; this obviously won't work, though, if the
clone is disconnected (on a laptop with no link, or something).
next prev parent reply other threads:[~2004-12-18 19:27 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 [this message]
2005-01-04 16:09 ` Kumar Gala
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=41C4849D.9060207@starnetworks.us \
--to=kpfleming@starnetworks.us \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=kumar.gala@freescale.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