git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schubert <mschub@elegosoft.com>
To: H Krishnan <hetchkay@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Using git-svn fetch after a directory change with rewrite-root
Date: Tue, 16 Aug 2011 13:26:43 +0200	[thread overview]
Message-ID: <4E4A53F3.6000200@elegosoft.com> (raw)
In-Reply-To: <loom.20110810T152000-152@post.gmane.org>

On 08/10/2011 03:22 PM, H Krishnan wrote: 
> What is the procedure for getting this change into git? Should I contact the 
> person who submitted the original patch?

See Documentation/SubmittingPatches in the Git source tree.

You should CC the people involved.

Cheers.

  reply	other threads:[~2011-08-16 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  3:26 Using git-svn fetch after a directory change with rewrite-root H Krishnan
2011-08-10 13:22 ` H Krishnan
2011-08-16 11:26   ` Michael Schubert [this message]
2011-08-20 19:18 ` Eric Wong
2011-09-01 20:54   ` Eric Wong

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=4E4A53F3.6000200@elegosoft.com \
    --to=mschub@elegosoft.com \
    --cc=git@vger.kernel.org \
    --cc=hetchkay@gmail.com \
    /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).