git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin Williams" <kevwil@gmail.com>
To: git@vger.kernel.org
Subject: git-p4 and changing p4 depot path
Date: Fri, 5 Sep 2008 10:47:25 -0600	[thread overview]
Message-ID: <683a886f0809050947k3b461495u459607dccf891698@mail.gmail.com> (raw)

I've got some code I've been working on in a local git repository that
I cloned from Perforce using git-p4. Now, I need to commit my changes
to a *different depot path* within Perforce. Since the p4 depot path
is stored in the logs rather than config, and logs are immutable
because commits are immutable, it seems I cannot do this. Is there any
way to do this? Why isn't the depot path stored in config? Please
help!

-- 
Cheers,

Kevin Williams
http://kevwil.com/

             reply	other threads:[~2008-09-05 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 16:47 Kevin Williams [this message]
2008-09-05 18:04 ` git-p4 and changing p4 depot path Tor Arvid Lund
2008-09-05 18:54   ` Kevin Williams

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=683a886f0809050947k3b461495u459607dccf891698@mail.gmail.com \
    --to=kevwil@gmail.com \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).